From: Tejun Heo <tj@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH] workqueue: Automatic affinity scope fallback for single-pod topologies
Date: Tue, 3 Feb 2026 10:43:15 -1000 [thread overview]
Message-ID: <aYJd46xHsiIgzOSs@slm.duckdns.org> (raw)
In-Reply-To: <8e66cf1a-09e2-4261-b2b4-6a5e608b9ec7@kernel.org>
Hello,
On Tue, Feb 03, 2026 at 03:34:22PM -0500, Chuck Lever wrote:
> The patch addresses that, I'd hope, by only switching to per-CPU on
> single pod (ie, simple) systems. Larger, more complicated, topologies
> should be left unchanged. I imagine that on a single pod machine with a
> large number of cores, having per-CPU locking will nearly always be a
> win.
Oh, I mean, unfortunately, intel produces chips with a lot of CPUs on a
single L3 cache. e.g. Recent intel chips have upto 128 cores per socket and
each socket still presents as a single L3 cache domain, so falling back to
AFFN_SMT would mean that all unbound workqueues by default would be backed
by 128 pools per socket. Create some hundreds of threads per pool and then
now you end up with hundreds of thousands of kworkers.
Thanks.
--
tejun
prev parent reply other threads:[~2026-02-03 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 14:37 Chuck Lever
2026-02-03 19:10 ` Tejun Heo
2026-02-03 20:14 ` Chuck Lever
2026-02-03 20:29 ` Tejun Heo
2026-02-03 20:34 ` Chuck Lever
2026-02-03 20:43 ` Tejun Heo [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=aYJd46xHsiIgzOSs@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jiangshanlai@gmail.com \
--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
all inboxes | Powered by JetHome®