mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH 0/4] Workqueue: replace system wq and change alloc_workqueue callers
Date: Fri, 15 Aug 2025 08:04:46 -1000	[thread overview]
Message-ID: <aJ92vqBchsh-h-0z@slm.duckdns.org> (raw)
In-Reply-To: <20250815094510.52360-1-marco.crivellari@suse.com>

Hello, Marco.

On Fri, Aug 15, 2025 at 11:45:06AM +0200, Marco Crivellari wrote:
> === Introduced Changes by this series ===
> 
> 1) [P 1-2] Replace use of system_wq and system_unbound_wq
> 
> 		system_wq is a per-CPU workqueue, but his name is not clear.
> 		system_unbound_wq is to be used when locality is not required.
> 		
> 		Because of that, system_wq has been renamed in system_percpu_wq, and
> 		system_unbound_wq has been renamed in system_dfl_wq.
> 
> 2) [P 3] add WQ_PERCPU to remaining alloc_workqueue() users 
> 
> 		Every alloc_workqueue() caller should use one among WQ_PERCPU or
> 		WQ_UNBOUND. This is actually enforced warning if both or none of them
> 		are present at the same time.
> 
> 		WQ_UNBOUND will be removed in a next release cycle.
> 		
> 3) [P 4] upgraded WQ_UNBOUND documentation
> 
> 		Added a note about the WQ_UNBOUND flag removal in a next release cycle.
> 		
> 		
> Per-subsystem changes will be submitted in different series inolving also
> maintainers.

I'm afraid these are a bit intrusive for me to apply directly. Can you
please split the patches in this and related serieses on subsystem tree
boundaries? e.g. Network flows through the same tree but different
filesystems often have their own trees. Please prefix the patch title with
the respective subsystem's name. As the base patch is already in the master
branch, you can ask each tree to take the patches. For trees that don't
respond after a couple pings, we can route them through wq tree.

Thanks.

-- 
tejun

  parent reply	other threads:[~2025-08-15 18:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15  9:45 Marco Crivellari
2025-08-15  9:45 ` [PATCH 1/4] Workqueue: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-08-15  9:45 ` [PATCH 2/4] Workqueue: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-08-15  9:45 ` [PATCH 3/4] Workqueue: WQ_PERCPU added to all the remaining users Marco Crivellari
2025-08-15  9:45 ` [PATCH 4/4] [Doc] Workqueue: WQ_UNBOUND doc upgraded Marco Crivellari
2025-08-15 18:04 ` Tejun Heo [this message]
2025-08-19  8:41   ` [PATCH 0/4] Workqueue: replace system wq and change alloc_workqueue callers Marco Crivellari
2025-08-20 23:22     ` Tejun Heo
2025-08-21  7:44       ` Marco Crivellari
2025-08-19 12:28   ` Marco Crivellari
2025-08-20 23:19     ` Tejun Heo
2025-08-21  7:40       ` Marco Crivellari
2025-08-21 20:29         ` Tejun Heo
2025-08-25 10:38           ` 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=aJ92vqBchsh-h-0z@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.crivellari@suse.com \
    --cc=mhocko@suse.com \
    --cc=tglx@linutronix.de \
    /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®