netdev - Re: [PATCH net-next v2 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <Z5e9H6dtwyrGQFfK@LQ3V64L9R2>
Date: Mon, 27 Jan 2025 12:06:39 -0500
From: Joe Damato <jdamato@...tly.com>
To: Samiullah Khawaja <skhawaja@...gle.com>
Cc: Jakub Kicinski <kuba@...nel.org>,
	"David S . Miller " <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
	almasrymina@...gle.com, netdev@...r.kernel.org,
	mkarsten@...terloo.ca
Subject: Re: [PATCH net-next v2 0/4] Add support to do threaded napi busy poll

On Thu, Jan 23, 2025 at 11:12:32PM +0000, Samiullah Khawaja wrote:
> Extend the already existing support of threaded napi poll to do continuous
> busy polling.
> 
> This is used for doing continuous polling of napi to fetch descriptors from
> backing RX/TX queues for low latency applications. Allow enabling of threaded
> busypoll using netlink so this can be enabled on a set of dedicated napis for
> low latency applications.
> 
> It allows enabling NAPI busy poll for any userspace application
> indepdendent of userspace API being used for packet and event processing
> (epoll, io_uring, raw socket APIs). Once enabled user can fetch the PID
> of the kthread doing NAPI polling and set affinity, priority and
> scheduler for it depending on the low-latency requirements.

When you resubmit this after the merge window (or if you resubmit it
as an RFC), would you mind CCing both me (jdamato@...tly.com) and
Martin (mkarsten@...terloo.ca) ?

We almost missed this revision after commenting on the previous
version, since we weren't included in the CC list.

Both Martin and I read through the cover letter and proposed changes
and have several questions/comments, but given that the thread is
marked as deferred/closed due to the merge window, we'll hold off
on digging in until the next revision is posted.