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>,
Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alex.bou9@gmail.com>
Subject: [PATCH 5/6] rapidio: rio: add WQ_PERCPU to alloc_workqueue users
Date: Tue, 5 May 2026 14:41:01 +0200 [thread overview]
Message-ID: <20260505124113.214297-6-marco.crivellari@suse.com> (raw)
In-Reply-To: <20260505124113.214297-1-marco.crivellari@suse.com>
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")
The refactoring is going to alter the default behavior of
alloc_workqueue() to be unbound by default.
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. For more details see the Link tag below.
In order to keep alloc_workqueue() behavior identical, explicitly request
WQ_PERCPU.
Cc: Matt Porter <mporter@kernel.crashing.org>
Cc: Alexandre Bounine <alex.bou9@gmail.com>
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>
---
drivers/rapidio/rio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rapidio/rio.c b/drivers/rapidio/rio.c
index 0c175e6d424f..f45e58b0971f 100644
--- a/drivers/rapidio/rio.c
+++ b/drivers/rapidio/rio.c
@@ -1994,7 +1994,7 @@ int rio_init_mports(void)
* TODO: Implement restart of discovery process for all or
* individual discovering mports.
*/
- rio_wq = alloc_workqueue("riodisc", 0, 0);
+ rio_wq = alloc_workqueue("riodisc", WQ_PERCPU, 0);
if (!rio_wq) {
pr_err("RIO: unable allocate rio_wq\n");
goto no_disc;
--
2.53.0
next prev parent reply other threads:[~2026-05-05 12:41 UTC|newest]
Thread overview: 11+ 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 ` Marco Crivellari [this message]
2026-05-05 12:41 ` [PATCH 6/6] umh: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
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
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-6-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=alex.bou9@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mporter@kernel.crashing.org \
--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