netdev - Re: [PATCH RESEND net-next 0/2] ntuple filters with RSS

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]

Message-ID: <4103a1aa-035b-85c2-6cd1-923a90cbb7d9@solarflare.com>
Date:   Fri, 2 Mar 2018 17:49:37 +0000
From:   David Riddoch <driddoch@...arflare.com>
To:     Edward Cree <ecree@...arflare.com>,
        David Miller <davem@...emloft.net>
CC:     <linux-net-drivers@...arflare.com>, <netdev@...r.kernel.org>,
        <linville@...driver.com>
Subject: Re: [PATCH RESEND net-next 0/2] ntuple filters with RSS


>> Lastly, there has been feedback asking how practical and useful this
>> facility actually is, and you must address that.
> According to our marketing folks, there is end-user demand for this feature
>   or something like it.
The main benefit comes on numa systems, when you have high throughput 
applications or containers on multiple numa nodes.  Using RSS without 
steering gives poor efficiency because traffic is often not received on 
the same node as the application.  With flow steering to a single queue 
you can get a bottleneck, as all traffic for a TCP/UDP port or container 
goes to one core.  ARFS doesn't scale to large numbers of flows.

This feature allows the admin to ensure packets are received on the same 
numa node as the application (improving efficiency) and avoids the 
single core bottleneck.

David