From: Cinq Prairie <notprairie@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Jakub Kicinski <kuba@kernel.org>,
Stefan Roesch <shr@devkernel.io>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] io_uring/napi: don't end the single NAPI busy poll early on need_resched()
Date: Tue, 3 Nov 2026 18:44:01 +0100 [thread overview]
Message-ID: <20261103174401.5520-1-notprairie@gmail.com> (raw)
In-Reply-To: <20261027204840.7823-1-notprairie@gmail.com>
On Tue, 27 Oct 2026 21:48:40 +0100, Cinq Prairie wrote:
> With a single registered NAPI, io_napi_blocking_busy_loop() hands
> io_napi_busy_loop_should_end() to napi_busy_loop_rcu() as loop_end and
> runs its own loop once, relying on __napi_busy_loop() to spin until
> that predicate fires.
Ping. v2 follows the approach you suggested in the v1 thread (absolute
deadline, fast path kept).
prev parent reply other threads:[~2026-11-03 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 20:48 Cinq Prairie
2026-11-03 17:44 ` Cinq Prairie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261103174401.5520-1-notprairie@gmail.com \
--to=notprairie@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shr@devkernel.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®