From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring <io-uring@vger.kernel.org>, 是参差 <shicenci@gmail.com>
Subject: Re: [PATCH] io_uring/fdinfo: be a bit nicer when looping a lot of SQEs/CQEs
Date: Tue, 3 Feb 2026 10:54:23 -0700 [thread overview]
Message-ID: <aYI2T75jvb-xeHmr@kbusch-mbp> (raw)
In-Reply-To: <f8f9a810-3e66-4010-b6c8-47cd9d1c9292@kernel.dk>
On Tue, Feb 03, 2026 at 10:06:18AM -0700, Jens Axboe wrote:
> Add cond_resched() in those dump loops, just in case a lot of entries
> are being dumped. And detect invalid CQ ring head/tail entries, to avoid
Hey, another cond_resched that lazy preemption would make unnecessary!
Looks good anyway.
Reviewed-by: Keith Busch <kbusch@kernel.org>
next prev parent reply other threads:[~2026-02-03 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:06 [PATCH] io_uring/fdinfo: be a bit nicer when looping a lot of SQEs/CQEs Jens Axboe
2026-02-03 17:54 ` Keith Busch [this message]
2026-02-03 17:56 ` Jens Axboe
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=aYI2T75jvb-xeHmr@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=shicenci@gmail.com \
/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