]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
scsi: scsi_transport_fc: WQ_PERCPU added to alloc_workqueue users()
authorMarco Crivellari <marco.crivellari@suse.com>
Fri, 31 Oct 2025 09:56:43 +0000 (10:56 +0100)
committerMartin K. Petersen <martin.petersen@oracle.com>
Thu, 13 Nov 2025 02:28:26 +0000 (21:28 -0500)
commitf76e4e1e836df41f602fa4c85f64f09e2a99266e
tree5bc3d46c1e90d6d1a6c0dd811bc405ff2a564095
parentafad6b34defed8ca19f8593b692024e8e296287f
scsi: scsi_transport_fc: WQ_PERCPU added to alloc_workqueue users()

Currently if a user enqueue 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 consistentcy 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 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>
Reviewed-by: Justin Tee <justin.tee@broadcom.com>
Link: https://patch.msgid.link/20251031095643.74246-5-marco.crivellari@suse.com
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
drivers/scsi/scsi_transport_fc.c