From: Marco Crivellari <marco.crivellari@suse.com>
To: linux-kernel@vger.kernel.org, platform-driver-x86@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>,
Maximilian Luz <luzmaximilian@gmail.com>,
Hans de Goede <hansg@kernel.org>,
Ilpo Jarvinen <ilpo.jarvinen@linux.intel.com>
Subject: [PATCH v2 0/3] replace uses of system_wq with system_percpu_wq, request alloc_workqueue to be per-cpu
Date: Thu, 27 Nov 2025 15:41:22 +0100 [thread overview]
Message-ID: <20251127144125.233728-1-marco.crivellari@suse.com> (raw)
Hi,
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")
More information can be found at the link below:
https://lore.kernel.org/all/20250221112003.1dSuoGyc@linutronix.de/
=== Changes introduced by this series ===
1) [P 1] Request alloc_workqueue() to be per-cpu if WQ_UNBOUND is not present
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.
2) [P 2-3]
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.
Thanks!
---
Changes in v2:
- Patches grouped in 1 single series
- commit logs improved
Marco Crivellari (3):
platform/surface: acpi-notify: add WQ_PERCPU to alloc_workqueue users
platform: x86: replace use of system_wq with system_percpu_wq
platform: surface: replace use of system_wq with system_percpu_wq
drivers/platform/surface/aggregator/ssh_packet_layer.c | 2 +-
drivers/platform/surface/aggregator/ssh_request_layer.c | 2 +-
drivers/platform/surface/surface_acpi_notify.c | 2 +-
drivers/platform/x86/gpd-pocket-fan.c | 4 ++--
drivers/platform/x86/x86-android-tablets/vexia_atla10_ec.c | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
--
2.51.1
next reply other threads:[~2025-11-27 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 14:41 Marco Crivellari [this message]
2025-11-27 14:41 ` [PATCH v2 1/3] platform/surface: acpi-notify: add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2025-11-27 14:41 ` [PATCH v2 2/3] platform: x86: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-11-27 14:41 ` [PATCH v2 3/3] platform: surface: " Marco Crivellari
2025-11-28 10:25 ` [PATCH v2 0/3] replace uses of system_wq with system_percpu_wq, request alloc_workqueue to be per-cpu Ilpo Järvinen
2025-11-28 16:28 ` 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=20251127144125.233728-1-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=mhocko@suse.com \
--cc=platform-driver-x86@vger.kernel.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
all inboxes | Powered by JetHome®