From: Daniel Borkmann <daniel@iogearbox.net>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
Derek Ditch <derek.ditch@gmail.com>
Cc: netdev@vger.kernel.org, tom@herbertland.com, jiri@resnulli.us,
willemb@google.com, eric@regit.org
Subject: Re: [Bug 120441] af_packet no longer uses symmetric hashing
Date: Thu, 16 Jun 2016 17:18:20 +0200 [thread overview]
Message-ID: <5762C33C.7030404@iogearbox.net> (raw)
In-Reply-To: <40238392-1c86-53ce-7722-51dd5c2dc294@stressinduktion.org>
On 06/16/2016 04:50 PM, Hannes Frederic Sowa wrote:
> On 16.06.2016 16:37, Daniel Borkmann wrote:
>> On 06/16/2016 03:57 PM, Derek Ditch wrote:
>> [...]
>>>> Begin forwarded message:
>>>>
>>>> From: bugzilla-daemon@bugzilla.kernel.org
>>>> Subject: [Bug 120441] af_packet no longer uses symmetric hashing
>>>> Date: June 16, 2016 at 07:35:54 -0500
>>>> To: derek.ditch@gmail.com
>>>>
>>>> https://bugzilla.kernel.org/show_bug.cgi?id=120441
>>
>> Just thinking out loud, perhaps one way would be to implement your own
>> fanout
>> hashing via eBPF demuxer, f.e. in case CPU selection etc wouldn't work.
>> Another
>> option could be to have a (2nd) customizable hash demux that would
>> enforce to
>> always go through the flow-dissector and where you would have a socket
>> option
>> to control keys for it, but I presume that seems rather less desirable.
>
> Isn't a symmetric hashing for af-packet something very fundamental?
> Looks much more like a bug to me.
I agree it would be useful resp. fundamental. I'm not quite sure whether
PACKET_FANOUT_HASH always had this guarantee since the initial implementation
f.e. depending on whether the skb got fanout demuxed from RX or TX paths,
you would either use a hw hash or it would have gone through the kernel's
(predecessor) flow dissector (and therefore potentially to different packet
sockets eventually). It might be the case that this got noticed due to the
flow dissector nowadays collecting more input for building its hash, hmm.
> Bye,
> Hannes
>
next prev parent reply other threads:[~2016-06-16 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <511F6A17-BD35-4846-A717-1463B74D7F2A@gmail.com>
2016-06-16 14:37 ` [Bug 120441] af_packet no longer uses symmetric hashing Daniel Borkmann
2016-06-16 14:40 ` Derek Ditch
2016-06-16 14:50 ` Hannes Frederic Sowa
2016-06-16 15:18 ` Daniel Borkmann [this message]
2016-06-16 15:32 ` Willem de Bruijn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5762C33C.7030404@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=derek.ditch@gmail.com \
--cc=eric@regit.org \
--cc=hannes@stressinduktion.org \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.com \
--cc=willemb@google.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;
as well as URLs for NNTP newsgroup(s).