Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net, Tom Herbert <tom@herbertland.com>,
	Jiri Pirko <jiri@resnulli.us>
Subject: Re: [Cake] the evolving skb_flow_dissect functions in linux 4.x?
Date: Mon, 25 May 2015 12:27:13 -0700	[thread overview]
Message-ID: <CAA93jw7VAvDGSTH0026ZtmWE7RDekG+u1fPaCnNBzeywQ9AxpQ@mail.gmail.com> (raw)
In-Reply-To: <B6767F65-EE59-40D3-A88C-A9D0A4BDBF96@gmail.com>

On Sun, May 24, 2015 at 9:51 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 22 May, 2015, at 21:36, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> B) I was wondering as to the proper new api to bring over src and/or
>> dest only hashing to the new stuff.
>
> From my point of view, I would like to see both the complete 5-tuple “flows" hash and individual srchost and dsthost hashes, such that I can XOR the latter two together to get a combined “hosts” hash.  Having those available simultaneously would let me do some very neat things in sch_cake, and potentially other future work too.

I have a working 4.1rc3 version now but it is either without or with
the 5 tuple hash. Still haven't decoded how to use the api.

I would like to also have something that could use a dest mac hash
instead, this would (with an increased quantum) make it possible to
look harder
at per-station queuing (at this layer) for wifi. (still, think we need
to be working at the mac80211 layer for that, but...)

>
>  - Jonathan Morton
>



-- 
Dave Täht
Open Networking needs **Open Source Hardware**

https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67

      reply	other threads:[~2015-05-25 19:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 18:36 Dave Taht
2015-05-25  4:51 ` Jonathan Morton
2015-05-25 19:27   ` Dave Taht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw7VAvDGSTH0026ZtmWE7RDekG+u1fPaCnNBzeywQ9AxpQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=jiri@resnulli.us \
    --cc=tom@herbertland.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox