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>, Breno Leitao <leitao@debian.org>
Subject: [PATCH RFC 2/2] docs: workqueue: Update WQ_PERCPU documentation
Date: Thu, 9 Jul 2026 12:25:10 +0200 [thread overview]
Message-ID: <20260709102510.180513-3-marco.crivellari@suse.com> (raw)
In-Reply-To: <20260709102510.180513-1-marco.crivellari@suse.com>
Update WQ_PERCPU documentation putting toghether the unbound description,
but removing the WQ_UNBOUND title, because this will now be the default
workqueue behavior.
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>
---
Documentation/core-api/workqueue.rst | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/core-api/workqueue.rst b/Documentation/core-api/workqueue.rst
index 411e1b28b8de..04135a104c25 100644
--- a/Documentation/core-api/workqueue.rst
+++ b/Documentation/core-api/workqueue.rst
@@ -187,9 +187,8 @@ resources, scheduled and executed.
Work items queued to a per-cpu wq are bound to a specific CPU.
This flag is the right choice when cpu locality is important.
- This flag is the complement of ``WQ_UNBOUND``.
+ Workqueue allocated without ``WQ_PERCPU`` are unbound by default.
-``WQ_UNBOUND``
Work items queued to an unbound wq are served by the special
worker-pools which host workers which are not bound to any
specific CPU. This makes the wq behave as a simple execution
--
2.54.0
next prev parent reply other threads:[~2026-07-09 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 10:25 [PATCH RFC 0/2] workqueue: Make alloc_workqueue() unbound by default Marco Crivellari
2026-07-09 10:25 ` [PATCH RFC 1/2] workqueue: Make unbound the default alloc_workqueue() behavior Marco Crivellari
2026-07-09 10:25 ` Marco Crivellari [this message]
2026-07-09 22:19 ` [PATCH RFC 0/2] workqueue: Make alloc_workqueue() unbound by default Tejun Heo
2026-07-10 7:16 ` 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=20260709102510.180513-3-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.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®