From: Tejun Heo <tj@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>, Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH v3 1/2] workqueue: Make alloc_workqueue() unbound by default
Date: Fri, 04 Sep 2026 07:01:40 -1000 [thread overview]
Message-ID: <d0f2a6dd88101fc30b41f7dfdcb46f8d@kernel.org> (raw)
In-Reply-To: <20260904141421.287647-2-marco.crivellari@suse.com>
Hello, Marco.
On Fri, Sep 04, 2026 at 04:14:20PM +0200, Marco Crivellari wrote:
> Currently alloc_workqueue() ensure that one among WQ_PERCPU or WQ_UNBOUND
> is present. Now every user has one among these two flags.
rvu_afpf_flr in drivers/net/ethernet/marvell/octeontx2/af/rvu.c got missed
and still has neither.
> + flags |= WQ_PERCPU;
This isn't mentioned in the description or the documentation. Patch 2 says
workqueues without WQ_PERCPU are unbound, which is now false for WQ_BH, and
the WQ_BH section still says WQ_HIGHPRI is the only allowed additional flag.
Please update both.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-09-04 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 14:14 [PATCH v3 0/2] workqueue: Make WQ_UNBOUND the default behavior Marco Crivellari
2026-09-04 14:14 ` [PATCH v3 1/2] workqueue: Make alloc_workqueue() unbound by default Marco Crivellari
2026-09-04 17:01 ` Tejun Heo [this message]
2026-09-04 14:14 ` [PATCH v3 2/2] doc: Update WQ_UNBOUND documentation 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=d0f2a6dd88101fc30b41f7dfdcb46f8d@kernel.org \
--to=tj@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
/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®