From: Jens Axboe <axboe@kernel.dk>
To: Li Chen <me@linux.beauty>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
io-uring <io-uring@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] io_uring/io-wq: let workers exit when unused
Date: Tue, 3 Feb 2026 07:09:42 -0700 [thread overview]
Message-ID: <0b9539f3-d30e-47ba-b577-8b65855a05a0@kernel.dk> (raw)
In-Reply-To: <19c22785df1.288e39fb101919.2611884700541801815@linux.beauty>
On 2/3/26 12:47 AM, Li Chen wrote:
> Hi Jens,
>
> > If you still want a test, I'm happy to write it. Since you've already
> > > tweaked/applied the v1 series, I can send the test as a standalone
> > > follow-up patch (no v2).
> > >
> > > If kselftest is preferred, I'll base it on the same CRIU-style workload:
> > > spawn iou-wrk-* via io_uring, quiesce/close the last ring, and check the
> > > worker exits within a short timeout.
> >
> > That sounds like the right way to do the test. Preferably a liburing
> > test/ case would be better, we don't do a lot of in-kernel selftests so
> > far. But liburing has everything.
>
> Thanks for your suggestion. I just adapted my local test program to
> liburing and posted the liburing PR here:
> https://github.com/axboe/liburing/pull/1529
Thanks, merged!
--
Jens Axboe
prev parent reply other threads:[~2026-02-03 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 14:37 [PATCH v1 0/2] io_uring/io-wq: let workers exit when unused Li Chen
2026-02-02 14:37 ` [PATCH v1 1/2] io-wq: add exit-on-idle mode Li Chen
2026-02-02 14:52 ` Jens Axboe
2026-02-02 15:14 ` Jens Axboe
2026-02-02 14:37 ` [PATCH v1 2/2] io_uring: allow io-wq workers to exit when unused Li Chen
2026-02-02 15:21 ` [PATCH v1 0/2] io_uring/io-wq: let workers " Jens Axboe
2026-02-03 0:37 ` Li Chen
2026-02-03 2:29 ` Jens Axboe
2026-02-03 7:47 ` Li Chen
2026-02-03 14:09 ` Jens Axboe [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=0b9539f3-d30e-47ba-b577-8b65855a05a0@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@linux.beauty \
/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