From: Marco Crivellari <marco.crivellari@suse.com>
To: linux-kernel@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>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 6/6] umh: replace use of system_unbound_wq with system_dfl_wq
Date: Tue, 5 May 2026 14:41:02 +0200 [thread overview]
Message-ID: <20260505124113.214297-7-marco.crivellari@suse.com> (raw)
In-Reply-To: <20260505124113.214297-1-marco.crivellari@suse.com>
This patch continues the effort to refactor workqueue APIs, which has begun
with the changes introducing new workqueues and a new alloc_workqueue flag:
commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
The point of the refactoring is to eventually alter the default behavior of
workqueues to become unbound by default so that their workload placement is
optimized by the scheduler.
Before that to happen, workqueue users must be converted to the better named
new workqueues with no intended behaviour changes:
system_wq -> system_percpu_wq
system_unbound_wq -> system_dfl_wq
This way the old obsolete workqueues (system_wq, system_unbound_wq) can be
removed in the future.
Cc: Luis Chamberlain <mcgrof@kernel.org>
Link: https://lore.kernel.org/all/20250221112003.1dSuoGyc@linutronix.de/
Suggested-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
---
kernel/umh.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/umh.c b/kernel/umh.c
index cffda97d961c..48117c569e1a 100644
--- a/kernel/umh.c
+++ b/kernel/umh.c
@@ -430,7 +430,7 @@ int call_usermodehelper_exec(struct subprocess_info *sub_info, int wait)
sub_info->complete = (wait == UMH_NO_WAIT) ? NULL : &done;
sub_info->wait = wait;
- queue_work(system_unbound_wq, &sub_info->work);
+ queue_work(system_dfl_wq, &sub_info->work);
if (wait == UMH_NO_WAIT) /* task has freed sub_info */
goto unlock;
--
2.53.0
next prev parent reply other threads:[~2026-05-05 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 12:40 [PATCH 0/6] Add WQ_PERCPU to alloc_workqueue users and workqueue replacement Marco Crivellari
2026-05-05 12:40 ` [PATCH 1/6] virt: acrn: Add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2026-05-05 12:40 ` [PATCH 2/6] media: synopsys: hdmirx: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2026-05-05 12:40 ` [PATCH 3/6] platform: cznic: turris-omnia-mcu: replace use of system_wq with system_percpu_wq Marco Crivellari
2026-05-05 14:22 ` Marek Behún
2026-05-05 12:41 ` [PATCH 4/6] media: ddbridge: add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2026-05-05 12:41 ` [PATCH 5/6] rapidio: rio: " Marco Crivellari
2026-05-05 12:41 ` Marco Crivellari [this message]
2026-05-05 17:16 ` [PATCH 0/6] Add WQ_PERCPU to alloc_workqueue users and workqueue replacement Tejun Heo
2026-05-05 21:47 ` Frederic Weisbecker
2026-05-06 6:35 ` Marco Crivellari
2026-05-07 21:38 ` Tejun Heo
2026-05-08 8:17 ` 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=20260505124113.214297-7-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--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®