From: Frederic Weisbecker <frederic@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v4 3/3] [Doc] Workqueue: add WQ_PERCPU
Date: Fri, 13 Jun 2025 15:13:11 +0200 [thread overview]
Message-ID: <aEwj52Fia2Q6-O2Z@localhost.localdomain> (raw)
In-Reply-To: <20250612133335.788593-4-marco.crivellari@suse.com>
Le Thu, Jun 12, 2025 at 03:33:35PM +0200, Marco Crivellari a écrit :
> 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>
Thanks, a few spelling nits below:
> ---
> 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.
s/that/a
> + This flag it's the right choice when cpu locality is important.
s/it's/is
> +
> + 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
in the future
> + items that dosen't need to be bound to a specific CPU, should not
s/dosen't/don't
> + use this flags.
flag.
But since the support for this is not there yet, perhaps this note
should be added later? Ie: if someone omits the WQ_UNBOUND flag currently,
the workqueue will be percpu.
Thanks.
> +
> ``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
>
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2025-06-13 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 13:33 [PATCH v4 0/3] Workqueue: add WQ_PERCPU, system_dfl_wq and system_percpu_wq Marco Crivellari
2025-06-12 13:33 ` [PATCH v4 1/3] Workqueue: add system_percpu_wq and system_dfl_wq Marco Crivellari
2025-06-13 13:05 ` Frederic Weisbecker
2025-06-13 13:19 ` Marco Crivellari
2025-06-12 13:33 ` [PATCH v4 2/3] Workqueue: add new WQ_PERCPU flag Marco Crivellari
2025-06-12 13:33 ` [PATCH v4 3/3] [Doc] Workqueue: add WQ_PERCPU Marco Crivellari
2025-06-13 13:13 ` Frederic Weisbecker [this message]
2025-06-13 13:23 ` 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=aEwj52Fia2Q6-O2Z@localhost.localdomain \
--to=frederic@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--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