All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: Ming Lei <tom.leiming@gmail.com>,
	axboe@kernel.dk, hare@suse.de, sean@ashe.io, neelx@suse.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] blk-mq: dispatch kworker to housekeeping CPU when hctx cpumask is empty
Date: Wed, 14 Oct 2026 09:34:04 -1000	[thread overview]
Message-ID: <adebd7c36fe4c6e349aca65bd7820079@kernel.org> (raw)
In-Reply-To: <pvnvyzf3cbebpxmobjntvovrruxgnygm7pwgx3tl2jczc7ji5z@ygmd6z4cfxh4>

Hello, Aaron.

On Mon, Oct 12, 2026 at 12:06:25PM -0400, Aaron Tomlin wrote:
> kblockd_workqueue is unique in that it is allocated as WQ_PERCPU to
> preserve per-CPU locality for multi-queue devices.

I haven't followed the earlier discussion, but if CPU locality is important
without requiring hard per-CPU affinity, an unbound workqueue with
non-strict "cpu" (or "smt" for core) affinity scope can provide both:
locality by default with flexibility to migrate when needed.

Thanks.

-- 
tejun

  parent reply	other threads:[~2026-10-14 19:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12  1:29 [PATCH] blk-mq: dispatch kworker to housekeeping CPU when hctx cpumask is empty Aaron Tomlin
2026-10-12  1:56 ` Ming Lei
2026-10-12  2:21   ` Aaron Tomlin
2026-10-12  2:51     ` Ming Lei
2026-10-12 16:06       ` Aaron Tomlin
2026-10-13 12:28         ` Ming Lei
2026-10-13 13:33           ` Aaron Tomlin
2026-10-13 14:07             ` Ming Lei
2026-10-13 18:42               ` Aaron Tomlin
2026-10-14 19:34         ` Tejun Heo [this message]
2026-10-15  1:26           ` Aaron Tomlin

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=adebd7c36fe4c6e349aca65bd7820079@kernel.org \
    --to=tj@kernel.org \
    --cc=atomlin@atomlin.com \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neelx@suse.com \
    --cc=sean@ashe.io \
    --cc=stable@vger.kernel.org \
    --cc=tom.leiming@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.