From: Breno Leitao <leitao@debian.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [RFC PATCH 0/2] workqueue: Add wornings and check WQ flags usage
Date: Fri, 15 May 2026 05:17:04 -0700 [thread overview]
Message-ID: <agcOg3CDZH-UDkjg@gmail.com> (raw)
In-Reply-To: <20260514092354.125149-1-marco.crivellari@suse.com>
On Thu, May 14, 2026 at 11:23:52AM +0200, Marco Crivellari wrote:
> Hi,
>
> Currently system_wq and system_unbound_wq can still be used and no message
> is printed. To avoid further use of them, add a warning and route the
> workqueue on system_percpu_wq or system_dfl_wq.
>
> Similar scenario for WQ_PERCPU and WQ_UNBOUND. Currently there are still
> users that use alloc_workqueue(,0,). To avoid such situations, a couple
> of checks have been added:
>
> - if neither of the flag is present, set WQ_PERCPU
> - if both are present, remove WQ_PERCPU
>
> Along with these, a warning will be printed.
How many users will seee this warning once this patch lands?
next prev parent reply other threads:[~2026-05-15 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 9:23 [RFC PATCH 0/2] workqueue: Add wornings and check WQ flags usage Marco Crivellari
2026-05-14 9:23 ` [RFC PATCH 1/2] workqueue: Add warn and fallback if system_{unbound}_wq is used Marco Crivellari
2026-05-14 9:23 ` [RFC PATCH 2/2] workqueue: Add warnings and ensure one among WQ_PERCPU or WQ_UNBOUND is present Marco Crivellari
2026-05-15 9:09 ` Marco Crivellari
2026-05-15 12:17 ` Breno Leitao [this message]
2026-05-15 13:25 ` [RFC PATCH 0/2] workqueue: Add wornings and check WQ flags usage 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=agcOg3CDZH-UDkjg@gmail.com \
--to=leitao@debian.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=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