From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net, 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 07:51:34 +0300 [thread overview]
Message-ID: <B6767F65-EE59-40D3-A88C-A9D0A4BDBF96@gmail.com> (raw)
In-Reply-To: <CAA93jw6Y3H5H4_MVAxTqt2QvdBRQtSRGQEZ5_2T91j+sXKrhRw@mail.gmail.com>
> 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.
- Jonathan Morton
next prev parent reply other threads:[~2015-05-25 4:51 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 [this message]
2015-05-25 19:27 ` Dave Taht
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=B6767F65-EE59-40D3-A88C-A9D0A4BDBF96@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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