From: Jens Axboe <axboe@kernel.dk>
To: Li Chen <me@linux.beauty>,
Pavel Begunkov <asml.silence@gmail.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] io-wq: add exit-on-idle mode
Date: Mon, 2 Feb 2026 08:14:03 -0700 [thread overview]
Message-ID: <8d675e0b-346d-44f1-b21b-e6c36d9230e9@kernel.dk> (raw)
In-Reply-To: <20260202143755.789114-2-me@linux.beauty>
On 2/2/26 7:37 AM, Li Chen wrote:
> diff --git a/io_uring/io-wq.c b/io_uring/io-wq.c
> index 5d0928f37471..97e7eb847c6e 100644
> --- a/io_uring/io-wq.c
> +++ b/io_uring/io-wq.c
> @@ -655,6 +656,18 @@ static int io_wq_worker(void *data)
> io_worker_handle_work(acct, worker);
>
> raw_spin_lock(&wq->lock);
> + /*
> + * If wq is marked idle-exit, drop this worker as soon as it
> + * becomes idle. This is used to avoid keeping io-wq worker
> + * threads around for tasks that no longer have any active
> + * io_uring instances.
> + */
> + if (test_bit(IO_WQ_BIT_EXIT_ON_IDLE, &wq->state)) {
> + acct->nr_workers--;
> + raw_spin_unlock(&wq->lock);
> + __set_current_state(TASK_RUNNING);
> + break;
> + }
> /*
> * Last sleep timed out. Exit if we're not the last worker,
> * or if someone modified our affinity.
One more note - just add this test_bit() to the check right below, then
you avoid duplicating all of that exit logic. They do the exact same
thing.
--
Jens Axboe
next prev parent reply other threads:[~2026-02-02 15:14 UTC|newest]
Thread overview: 6+ 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 [this message]
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
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=8d675e0b-346d-44f1-b21b-e6c36d9230e9@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