mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: [PATCH v2] workqueue: Automatic affinity scope fallback for single-pod topologies
Date: Thu, 5 Feb 2026 12:10:30 -1000	[thread overview]
Message-ID: <aYUVVuIidMpuYy3j@slm.duckdns.org> (raw)
In-Reply-To: <20260205024912.6753-1-cel@kernel.org>

Hello, Chuck.

On Wed, Feb 04, 2026 at 09:49:11PM -0500, Chuck Lever wrote:
> +static bool __init cpus_share_cluster(int cpu0, int cpu1)
> +{
> +	return cpumask_test_cpu(cpu0, topology_cluster_cpumask(cpu1));
> +}

Cluster boundary == core boundary for a lot of CPUs. I don't think this is
going to work. Here are a couple options:

- Introduce an affinity level which splits CACHE according to some
  adjustable heuristics.

- Make the NFS workqueue default to WQ_AFFN_CORE (or maybe switch based on
  some heuristics) or switch to a per-cpu workqueue.

Thanks.

-- 
tejun

  reply	other threads:[~2026-02-05 22:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05  2:49 Chuck Lever
2026-02-05 22:10 ` Tejun Heo [this message]
2026-02-05 23:29   ` Chuck Lever

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=aYUVVuIidMpuYy3j@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®