From: Marco Crivellari <marco.crivellari@suse.com>
To: linux-kernel@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Marco Crivellari <marco.crivellari@suse.com>,
Michal Hocko <mhocko@suse.com>
Subject: [PATCH v2 4/4] [Doc] Workqueue: add WQ_PERCPU
Date: Mon, 9 Jun 2025 12:35:35 +0200 [thread overview]
Message-ID: <20250609103535.780069-5-marco.crivellari@suse.com> (raw)
In-Reply-To: <20250609103535.780069-1-marco.crivellari@suse.com>
Workqueue documentation upgraded with the description
of the new added flag, WQ_PERCPU.
Also the WQ_UNBOUND flag documentation has been integrated
Suggested-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
---
Documentation/core-api/workqueue.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/core-api/workqueue.rst b/Documentation/core-api/workqueue.rst
index e295835fc116..ae63a648a51b 100644
--- a/Documentation/core-api/workqueue.rst
+++ b/Documentation/core-api/workqueue.rst
@@ -183,6 +183,12 @@ resources, scheduled and executed.
BH work items cannot sleep. All other features such as delayed queueing,
flushing and canceling are supported.
+``WQ_PERCPU``
+ Work items queued to a per-cpu wq are bound to that specific CPU.
+ This flag it's the right choice when cpu locality is important.
+
+ This flag is the complement of ``WQ_UNBOUND``.
+
``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
@@ -200,6 +206,10 @@ resources, scheduled and executed.
* Long running CPU intensive workloads which can be better
managed by the system scheduler.
+ **Note:** This flag will be removed in future and all the work
+ items that dosen't need to be bound to a specific CPU, should not
+ use this flags.
+
``WQ_FREEZABLE``
A freezable wq participates in the freeze phase of the system
suspend operations. Work items on the wq are drained and no
--
2.49.0
next prev parent reply other threads:[~2025-06-09 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 10:35 [PATCH v2 0/4] Workqueue: rename system workqueue and " Marco Crivellari
2025-06-09 10:35 ` [PATCH v2 1/4] Workqueue: add system_percpu_wq Marco Crivellari
2025-06-09 10:35 ` [PATCH v2 2/4] Workqueue: add system_dfl_wq Marco Crivellari
2025-06-10 3:04 ` Lai Jiangshan
2025-06-10 8:56 ` Marco Crivellari
2025-06-10 21:44 ` Tejun Heo
2025-06-09 10:35 ` [PATCH v2 3/4] Workqueue: add WQ_PERCPU Marco Crivellari
2025-06-10 2:07 ` kernel test robot
2025-06-09 10:35 ` Marco Crivellari [this message]
2025-06-09 18:59 ` [PATCH v2 0/4] Workqueue: rename system workqueue and " Tejun Heo
2025-06-10 8:34 ` Marco Crivellari
2025-06-10 21:38 ` Tejun Heo
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=20250609103535.780069-5-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=mhocko@suse.com \
--cc=tglx@linutronix.de \
--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®