mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-rt-devel@lists.linux.dev,
	"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	John Ogness <john.ogness@linutronix.de>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH v2 1/2] workqueue: Allow to expose ordered workqueues via sysfs
Date: Fri, 27 Feb 2026 07:12:46 -1000	[thread overview]
Message-ID: <aaHQjt8bZsFLBwfh@slm.duckdns.org> (raw)
In-Reply-To: <20260227170103.4042157-2-bigeasy@linutronix.de>

On Fri, Feb 27, 2026 at 06:01:02PM +0100, Sebastian Andrzej Siewior wrote:
> Ordered workqueues are not exposed via sysfs because the 'max_active'
> attribute changes the number actives worker. More than one active worker
> can break ordering guarantees.
> 
> This can be avoided by forbidding writes the file for ordered
> workqueues. Exposing it via sysfs allows to alter other attributes such
> as the cpumask on which CPU the worker can run.
> 
> The 'max_active' value shouldn't be changed for BH worker because the
> core never spawns additional worker and the worker itself can not be
> preempted. So this make no sense.
> 
> Allow to expose ordered workqueues via sysfs if requested and forbid
> changing 'max_active' value for ordered and BH worker.
> 
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>

Acked-by: Tejun Heo <tj@kernel.org>

I can apply this to wq/for-7.1. Would that work?

Thanks.

-- 
tejun

  reply	other threads:[~2026-02-27 17:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 17:01 [PATCH v2 0/2] efi: Expose the runtime-services workqueue " Sebastian Andrzej Siewior
2026-02-27 17:01 ` [PATCH v2 1/2] workqueue: Allow to expose ordered workqueues " Sebastian Andrzej Siewior
2026-02-27 17:12   ` Tejun Heo [this message]
2026-02-27 17:14     ` Sebastian Andrzej Siewior
2026-02-27 17:20       ` Ard Biesheuvel
2026-02-27 17:27         ` Tejun Heo
2026-02-27 17:36           ` Ard Biesheuvel
2026-02-27 17:01 ` [PATCH v2 2/2] efi: Allow to expose the workqueue " Sebastian Andrzej Siewior
2026-02-27 19:10 ` [PATCH v2 0/2] efi: Expose the runtime-services " 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=aaHQjt8bZsFLBwfh@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=ardb@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jiangshanlai@gmail.com \
    --cc=john.ogness@linutronix.de \
    --cc=lgoncalv@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    /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®