netdev - Re: [PATCH] Add a 'start N' option when specifying the Rx flow hash indirection table.

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 1 Apr 2019 20:30:19 +0100
From:   Edward Cree <ecree@...arflare.com>
To:     Jonathan Lemon <jonathan.lemon@...il.com>,
        "John W. Linville" <linville@...driver.com>
CC:     <netdev@...r.kernel.org>, <kernel-team@...com>
Subject: Re: [PATCH] Add a 'start N' option when specifying the Rx flow hash
 indirection table.

On 01/04/2019 19:42, Jonathan Lemon wrote:
> When using more than one RSS table, specifying a starting queue for flow distibution
> makes it easier to specify the set of queues attached to the table.  An example:
>
>   ethtool -X eth0 context 0 equal 14			# queues  0 .. 13
>   ethtool -X eth0 context 1 start 14 equal 42		# queues 14 .. 56
>   ethtool -N eth0 flow-type udp6 dst-port 4242 context 1
>
> Here, context 0 might be handling normal kernel traffic, while context 1 handles
> AF_XDP traffic.
>
> Signed-off-by: Jonathan Lemon <jonathan.lemon@...il.com>
Acked-by: Edward Cree <ecree@...arflare.com>