Re: [PATCH v4 1/2] workqueue: Make alloc_workqueue() unbound by default
From: Marco Crivellari
Date: Fri Oct 16 2026 - 09:04:01 EST
On Fri, Oct 16, 2026 at 1:45 PM Breno Leitao <leitao@xxxxxxxxxx> wrote:
>
> On Thu, Oct 15, 2026 at 04:01:47PM +0200, Marco Crivellari wrote:
> > + if (unlikely(wq_unbound_by_default))
> > + pr_warn_once("workqueue: %s is using neither WQ_PERCPU or WQ_UNBOUND. "
> > + "Setting WQ_UNBOUND.\n", wq->name);
>
> Why do we need to warn here? With this new approach, shouldn't users be
> able to rely on WQ_UNBOUND being the default and leave it out?
Yes, it was mostly to ensure users notice the change in behavior when
flags are not specified.
But I can remove it for the next version.
Thanks!
--
Marco Crivellari
SUSE Labs