From: Bjorn Helgaas <helgaas@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Ilpo Jarvinen <ilpo.jarvinen@linux.intel.com>,
Manivannan Sadhasivam <mani@kernel.org>
Subject: Re: [PATCH] PCI: shpchp: add WQ_PERCPU to alloc_workqueue users
Date: Mon, 29 Dec 2025 10:40:59 -0600 [thread overview]
Message-ID: <20251229164059.GA65997@bhelgaas> (raw)
In-Reply-To: <20251107143624.244978-1-marco.crivellari@suse.com>
[+cc Mani]
On Fri, Nov 07, 2025 at 03:36:24PM +0100, Marco Crivellari wrote:
> Currently if a user enqueues a work item using schedule_delayed_work() the
> used wq is "system_wq" (per-cpu wq) while queue_delayed_work() use
> WORK_CPU_UNBOUND (used when a cpu is not specified). The same applies to
> schedule_work() that is using system_wq and queue_work(), that makes use
> again of WORK_CPU_UNBOUND.
> This lack of consistency cannot be addressed without refactoring the API.
>
> alloc_workqueue() treats all queues as per-CPU by default, while unbound
> workqueues must opt-in via WQ_UNBOUND.
>
> This default is suboptimal: most workloads benefit from unbound queues,
> allowing the scheduler to place worker threads where they’re needed and
> reducing noise when CPUs are isolated.
>
> This continues the effort to refactor workqueue APIs, which began with
> the introduction of new workqueues and a new alloc_workqueue flag in:
>
> commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
> commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
>
> This change adds a new WQ_PERCPU flag to explicitly request
> alloc_workqueue() to be per-cpu when WQ_UNBOUND has not been specified.
>
> With the introduction of the WQ_PERCPU flag (equivalent to !WQ_UNBOUND),
> any alloc_workqueue() caller that doesn’t explicitly specify WQ_UNBOUND
> must now use WQ_PERCPU.
>
> Once migration is complete, WQ_UNBOUND can be removed and unbound will
> become the implicit default.
>
> Suggested-by: Tejun Heo <tj@kernel.org>
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
Squashed with similar patches [1] and applied on pci/workqueue for
v6.20, thanks!
See https://lore.kernel.org/r/20251229163858.GA63361@bhelgaas
> ---
> drivers/pci/hotplug/shpchp_core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/hotplug/shpchp_core.c b/drivers/pci/hotplug/shpchp_core.c
> index 0c341453afc6..56308515ecba 100644
> --- a/drivers/pci/hotplug/shpchp_core.c
> +++ b/drivers/pci/hotplug/shpchp_core.c
> @@ -80,7 +80,8 @@ static int init_slots(struct controller *ctrl)
> slot->device = ctrl->slot_device_offset + i;
> slot->number = ctrl->first_slot + (ctrl->slot_num_inc * i);
>
> - slot->wq = alloc_workqueue("shpchp-%d", 0, 0, slot->number);
> + slot->wq = alloc_workqueue("shpchp-%d", WQ_PERCPU, 0,
> + slot->number);
> if (!slot->wq) {
> retval = -ENOMEM;
> goto error_slot;
> --
> 2.51.1
>
next prev parent reply other threads:[~2025-12-29 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 14:36 [PATCH] PCI: shpchp: add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2025-12-24 15:16 ` Marco Crivellari
2025-12-29 16:40 ` Bjorn Helgaas [this message]
2025-12-30 10:06 ` Marco Crivellari
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=20251229164059.GA65997@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox