From: Marco Crivellari <marco.crivellari@suse.com>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Marco Crivellari <marco.crivellari@suse.com>,
Michal Hocko <mhocko@suse.com>,
"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: [PATCH 0/4] replace old wq(s), added WQ_PERCPU to alloc_workqueue
Date: Fri, 31 Oct 2025 10:56:39 +0100 [thread overview]
Message-ID: <20251031095643.74246-1-marco.crivellari@suse.com> (raw)
Hi,
=== Current situation: problems ===
Let's consider a nohz_full system with isolated CPUs: wq_unbound_cpumask is
set to the housekeeping CPUs, for !WQ_UNBOUND the local CPU is selected.
This leads to different scenarios if a work item is scheduled on an
isolated CPU where "delay" value is 0 or greater then 0:
schedule_delayed_work(, 0);
This will be handled by __queue_work() that will queue the work item on the
current local (isolated) CPU, while:
schedule_delayed_work(, 1);
Will move the timer on an housekeeping CPU, and schedule the work there.
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 consistency cannot be addressed without refactoring the API.
=== Recent changes to the WQ API ===
The following, address the recent changes in the Workqueue API:
- commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
- commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
The old workqueues will be removed in a future release cycle.
=== Introduced Changes by this series ===
1) [P 1] Replace uses of system_wq and system_unbound_wq
system_unbound_wq is to be used when locality is not required.
Because of that, system_unbound_wq has been replaced with
system_dfl_wq, to make clear it should be used when locality
is not required.
2) [P 2-3-4] WQ_PERCPU added to alloc_workqueue()
This change adds a new WQ_PERCPU flag to explicitly request
alloc_workqueue() to be per-cpu when WQ_UNBOUND has not been specified.
Thanks!
Marco Crivellari (4):
scsi: replace use of system_unbound_wq with system_dfl_wq
scsi: qla2xxx: WQ_PERCPU added to alloc_workqueue users
scsi: scsi_dh_alua: WQ_PERCPU added to alloc_workqueue users
scsi: scsi_transport_fc: WQ_PERCPU added to alloc_workqueue users
drivers/scsi/device_handler/scsi_dh_alua.c | 2 +-
drivers/scsi/qla2xxx/qla_os.c | 4 ++--
drivers/scsi/scsi_transport_fc.c | 5 +++--
drivers/scsi/scsi_transport_iscsi.c | 2 +-
4 files changed, 7 insertions(+), 6 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-31 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 9:56 Marco Crivellari [this message]
2025-10-31 9:56 ` [PATCH 1/4] scsi: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-10-31 9:56 ` [PATCH 2/4] scsi: qla2xxx: WQ_PERCPU added to alloc_workqueue users Marco Crivellari
2025-10-31 9:56 ` [PATCH 3/4] scsi: scsi_dh_alua: " Marco Crivellari
2025-10-31 9:56 ` [PATCH 4/4] scsi: scsi_transport_fc: " Marco Crivellari
2025-11-03 18:21 ` Justin Tee
2025-11-13 2:38 ` [PATCH 0/4] replace old wq(s), added WQ_PERCPU to alloc_workqueue Martin K. Petersen
2025-11-13 8:55 ` Marco Crivellari
2025-11-20 4:15 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2025-10-30 16:10 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=20251031095643.74246-1-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®