netdev - Re: [PATCH net-next v5 0/4] Add support to do threaded napi busy poll

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 for Android: free password hash cracker in your pocket

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

Message-ID: <b65404cb-cd51-40ad-a6a0-d7366391da7f@uwaterloo.ca>
Date: Mon, 28 Apr 2025 14:05:12 -0400
From: Martin Karsten <mkarsten@...terloo.ca>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>,
 Samiullah Khawaja <skhawaja@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
 "David S . Miller" <davem@...emloft.net>, Eric Dumazet
 <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
 almasrymina@...gle.com, willemb@...gle.com, jdamato@...tly.com
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next v5 0/4] Add support to do threaded napi busy poll

On 2025-04-28 12:52, Willem de Bruijn wrote:
> Martin Karsten wrote:
>> On 2025-04-24 16:02, Samiullah Khawaja wrote:

[snip]

> There is also a functional argument for this feature. It brings
> parity with userspace network stacks like DPDK and Google's SNAP [1].
> These also run packet (and L4+) network processing on dedicated cores,
> and by default do so in polling mode. An XDP plane currently lacks
> this well understood configuration. This brings it closer to parity.
I believe these existing user-level stacks burn one core per queue. This 
scheme burns two.