[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5762B9C0.9010902@iogearbox.net>
Date: Thu, 16 Jun 2016 16:37:52 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Derek Ditch <derek.ditch@...il.com>
CC: netdev@...r.kernel.org, tom@...bertland.com, jiri@...nulli.us,
willemb@...gle.com, eric@...it.org
Subject: Re: [Bug 120441] af_packet no longer uses symmetric hashing
On 06/16/2016 03:57 PM, Derek Ditch wrote:
[...]
>> Begin forwarded message:
>>
>> From: bugzilla-daemon@...zilla.kernel.org
>> Subject: [Bug 120441] af_packet no longer uses symmetric hashing
>> Date: June 16, 2016 at 07:35:54 -0500
>> To: derek.ditch@...il.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.
>> --- Comment #2 from Eric Leblond <eric@...it.org> ---
>> This patch has been introduced in 4.2.
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>> Begin forwarded message:
>>
>> From: bugzilla-daemon@...zilla.kernel.org
>> Subject: [Bug 120441] af_packet no longer uses symmetric hashing
>> Date: June 16, 2016 at 06:59:58 -0500
>> To: derek.ditch@...il.com
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=120441
>>
>> Eric Leblond <eric@...it.org> changed:
>>
>> What |Removed |Added
>> ----------------------------------------------------------------------------
>> CC| |eric@...it.org
>>
>> --- Comment #1 from Eric Leblond <eric@...it.org> ---
>> It seems the problem has been introduced by
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=42aecaa9bb2bd57eb8d61b4565cee5d3640863fb
>> where the symetrical jhash_3words function has been replaced by jhash2.
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>
>
Powered by blists - more mailing lists