mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Michal Hocko <mhocko@suse.com>, Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH v6 0/2] workqueue: Make WQ_UNBOUND the default behavior
Date: Wed, 18 Nov 2026 15:54:01 +0100	[thread overview]
Message-ID: <av28CfFtO8Hph1x7@localhost.localdomain> (raw)
In-Reply-To: <20261116155051.157875-1-marco.crivellari@suse.com>

Le Mon, Nov 16, 2026 at 04:50:49PM +0100, Marco Crivellari a écrit :
> Hi,
> 
> Currently alloc_workqueue() make sure one among WQ_UNBOUND or WQ_PERCPU is
> present with the current default being WQ_PERCPU.
> 
> Per-CPU workqueues provide strict CPU affinity and concurrency
> management. Some users rely on these properties, but many don't need
> them, and for those users per-CPU workqueues significantly restrict
> what the scheduler can do with their work items.
> 
> Unbound workqueues now use non-strict (soft) affinity scopes, so they
> keep part of the locality benefits while giving the scheduler more
> flexibility. This helps system-level concerns such as power management
> and CPU isolation.
> 
> This series therefore transitions alloc_workqueue() to unbound as the
> default. Users that need per-CPU behavior can still request it
> explicitly with WQ_PERCPU.
> 
> The behavior changes as follows:
> 
> [ P1 ]
> 
>   - keep WARN_ON() if WQ_PERCPU and WQ_UNBOUND are present and drop
>     WQ_PERCPU.
> 
>   - defaults to WQ_UNBOUND except for WQ_BH, that it is always per-CPU.
> 
>   - WQ_POWER_EFFICIENT description, kernel parameters and konfig
>     description changed to reflect what this patch introduces.
> 
> [ P2 ]
> 
>   Documentation updated accordingly.
> 
> Thanks!

That's a big step forward.

Thanks a lot!

-- 
Frederic Weisbecker
SUSE Labs

      parent reply	other threads:[~2026-11-18 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 15:50 Marco Crivellari
2026-11-16 15:50 ` [PATCH v6 1/2] workqueue: Make alloc_workqueue() unbound by default Marco Crivellari
2026-11-16 15:50 ` [PATCH v6 2/2] workqueue: doc: Update WQ_UNBOUND and WQ_BH documentation Marco Crivellari
2026-11-16 21:06 ` [PATCH v6 0/2] workqueue: Make WQ_UNBOUND the default behavior Tejun Heo
2026-11-18 14:54 ` Frederic Weisbecker [this message]

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=av28CfFtO8Hph1x7@localhost.localdomain \
    --to=frederic@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=jiangshanlai@gmail.com \
    --cc=leitao@debian.org \
    --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®