The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 v2 4/4] [Doc] Workqueue: WQ_UNBOUND doc upgraded
Date: Mon, 25 Aug 2025 15:57:45 +0200	[thread overview]
Message-ID: <aKxr2QH-4Vi8jHTU@localhost.localdomain> (raw)
In-Reply-To: <20250825132906.1050437-5-marco.crivellari@suse.com>

Le Mon, Aug 25, 2025 at 03:29:06PM +0200, Marco Crivellari a écrit :
> Doc upgraded to mention future removal of WQ_UNBOUND.
> 
> Suggested-by: Tejun Heo <tj@kernel.org>
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
> ---
>  Documentation/core-api/workqueue.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/core-api/workqueue.rst b/Documentation/core-api/workqueue.rst
> index 165ca73e8351..c8ece1c38808 100644
> --- a/Documentation/core-api/workqueue.rst
> +++ b/Documentation/core-api/workqueue.rst
> @@ -206,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 the future and all the work
> +  items that don't need to be bound to a specific CPU, should not
> +  use this flag.
> +

I would introduce that later, once WQ_PERCPU is correctly added everywhere and
we can assume that no flag means unbound.

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.50.1
> 

-- 
Frederic Weisbecker
SUSE Labs

      reply	other threads:[~2025-08-25 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 13:29 [PATCH v2 0/4] Workqueue: replace system wq and change alloc_workqueue callers Marco Crivellari
2025-08-25 13:29 ` [PATCH v2 1/4] Workqueue: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-08-25 13:55   ` Frederic Weisbecker
2025-08-25 13:29 ` [PATCH v2 2/4] Workqueue: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-08-25 13:49   ` Frederic Weisbecker
2025-08-25 13:29 ` [PATCH v2 3/4] Workqueue: WQ_PERCPU added to all the remaining users Marco Crivellari
2025-08-25 13:55   ` Frederic Weisbecker
2025-08-25 13:29 ` [PATCH v2 4/4] [Doc] Workqueue: WQ_UNBOUND doc upgraded Marco Crivellari
2025-08-25 13:57   ` Frederic Weisbecker [this message]

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=aKxr2QH-4Vi8jHTU@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