From: Frederic Weisbecker <frederic@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: Remove HK_TYPE_WQ from affecting wq_unbound_cpumask
Date: Tue, 31 Mar 2026 23:26:36 +0200 [thread overview]
Message-ID: <acw8DPxToGmaEVHu@pavilion.home> (raw)
In-Reply-To: <20260331183531.2791465-1-longman@redhat.com>
Le Tue, Mar 31, 2026 at 02:35:22PM -0400, Waiman Long a écrit :
> For historical reason, wq_unbound_cpumask is initially set as
> intersection of HK_TYPE_DOMAIN, HK_TYPE_WQ and workqueue.unbound_cpus
> boot command line option.
>
> At run time, users can update the unbound cpumask via the
> /sys/devices/virtual/workqueue/cpumask sysfs file. Creation
> and modification of cpuset isolated partitions will also update
> wq_unbound_cpumask based on the latest HK_TYPE_DOMAIN cpumask.
> The HK_TYPE_WQ cpumask is out of the picture with these runtime updates.
>
> Complete the transition by taking HK_TYPE_WQ out from the workqueue code
> and make it depends on HK_TYPE_DOMAIN only from the housekeeping side.
> The final goal is to eliminate HK_TYPE_WQ as a housekeeping cpumask type.
>
> Signed-off-by: Waiman Long <longman@redhat.com>
Acked-by: Frederic Weisbecker <frederic@kernel.org>
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2026-03-31 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 18:35 [PATCH] workqueue: Remove HK_TYPE_WQ from affecting wq_unbound_cpumask Waiman Long
2026-03-31 19:12 ` Tejun Heo
2026-03-31 21:26 ` Frederic Weisbecker [this message]
2026-03-31 21:47 ` Tejun Heo
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=acw8DPxToGmaEVHu@pavilion.home \
--to=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=tj@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 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.