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: [PATCH v4 2/2] doc: Update WQ_UNBOUND and WQ_BH documentation
Date: Fri, 16 Oct 2026 08:16:23 -0700 [thread overview]
Message-ID: <atI_vcVR6-CcB5M4@gmail.com> (raw)
In-Reply-To: <20261015140148.231126-3-marco.crivellari@suse.com>
On Thu, Oct 15, 2026 at 04:01:48PM +0200, Marco Crivellari wrote:
> When WQ_PERCPU is not present the default behavior is now WQ_UNBOUND,
> so update the documentation, reflecting this change.
>
> WQ_BH workqueues are the exception to this rule: they are always
> per-CPU and can't be unbound, so WQ_PERCPU is implicitly set for them
> regardless of what the caller passes. Update the WQ_BH section
> accordingly, as WQ_HIGHPRI is no longer the only additional flag
> involved.
>
> Link: https://lore.kernel.org/all/20250221112003.1dSuoGyc@linutronix.de/
> Suggested-by: Tejun Heo <tj@kernel.org>
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
Reviewed-by: Breno Leitao <leitao@debian.org>
next prev parent reply other threads:[~2026-10-16 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 14:01 [PATCH v4 0/2] workqueue: Make WQ_UNBOUND the default behavior Marco Crivellari
2026-10-15 14:01 ` [PATCH v4 1/2] workqueue: Make alloc_workqueue() unbound by default Marco Crivellari
2026-10-16 11:45 ` Breno Leitao
2026-10-16 12:57 ` Marco Crivellari
2026-10-16 15:53 ` Breno Leitao
2026-10-16 16:18 ` Marco Crivellari
2026-10-16 16:19 ` Marco Crivellari
2026-10-15 14:01 ` [PATCH v4 2/2] doc: Update WQ_UNBOUND and WQ_BH documentation Marco Crivellari
2026-10-16 15:16 ` Breno Leitao [this message]
2026-10-16 18:03 ` [PATCH v4 0/2] workqueue: Make WQ_UNBOUND the default behavior Tejun Heo
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=atI_vcVR6-CcB5M4@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
all inboxes | Powered by JetHome®