netdev - Re: [PATCH net-next] dpaa2-eth: Make Rx flow hash key configurable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20180924.122915.506780899873501609.davem@davemloft.net>
Date:   Mon, 24 Sep 2018 12:29:15 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     ruxandra.radulescu@....com
Cc:     netdev@...r.kernel.org, ioana.ciornei@....com
Subject: Re: [PATCH net-next] dpaa2-eth: Make Rx flow hash key configurable

From: Ioana Ciocoi Radulescu <ruxandra.radulescu@....com>
Date: Mon, 24 Sep 2018 15:36:21 +0000

> Until now, the Rx flow hash key was a 5-tuple (IP src, IP dst,
> IP nextproto, L4 src port, L4 dst port) fixed value that we
> configured at probe.
> 
> Add support for configuring this hash key at runtime.
> We support all standard header fields configurable through ethtool,
> but cannot differentiate between flow types, so the same hash key
> is applied regardless of protocol.
> 
> We also don't support the discard option.
> 
> Signed-off-by: Ioana Radulescu <ruxandra.radulescu@....com>

Applied.