From: Keith Busch <kbusch@kernel.org>
To: Ben Carey <benjamin.james.carey3@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] RCU hang with io_uring nvme polling
Date: Wed, 8 Jul 2026 07:35:00 -0600 [thread overview]
Message-ID: <ak5SBF1kDsgrGJiS@kbusch-mbp> (raw)
In-Reply-To: <CA+KFGSoGVBzsnhht5Opo2PCf33M0uiLjK7BNQ-t2DjTDudwXrw@mail.gmail.com>
On Sat, Jul 04, 2026 at 03:35:14PM -0400, Ben Carey wrote:
> I'm most definitely not qualified to suggest this as a passable alternative,
> but when polling a tagset, is there a way to check if the tagset's been
> completed by another thread? Maybe break out if, for each polled request,
> request->state == MQ_RQ_COMPLETE? I'm unsure how to translate the parameters in
> blk_hctx_poll into the set of requests being waited on.
The overhead to track individual requests this way would largely negate
any benefit to polling. A request could be reallocated and dispatched
before the polling loop sees that it's complete, so at the very least
you'd have to hold an extra reference on every request you are polling
for to prevent that before you can check their status.
next prev parent reply other threads:[~2026-07-08 13:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 15:09 [BUG] RCU hang with io_uring nvme polling Ben Carey
2026-06-26 15:17 ` Jens Axboe
2026-06-26 16:05 ` Keith Busch
2026-06-26 16:06 ` Jens Axboe
2026-06-26 16:33 ` Keith Busch
2026-06-26 16:35 ` Jens Axboe
2026-06-26 16:48 ` Keith Busch
[not found] ` <CA+KFGSoyCSRzgamm-38oyAtEsqd7wZZ8awL79P40x7a819EK4w@mail.gmail.com>
2026-06-26 17:41 ` Ben Carey
2026-07-03 17:20 ` Ben Carey
2026-07-04 17:01 ` Keith Busch
2026-07-04 19:35 ` Ben Carey
2026-07-04 19:38 ` Ben Carey
2026-07-08 13:35 ` Keith Busch [this message]
2026-06-29 20:47 ` Ben Carey
2026-06-29 21:40 ` Keith Busch
2026-06-29 22:04 ` Keith Busch
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=ak5SBF1kDsgrGJiS@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=benjamin.james.carey3@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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