mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>
Cc: linux-kernel@vger.kernel.org, Breno Leitao <leitao@debian.org>,
	 kernel-team@meta.com, marco.crivellari@suse.com
Subject: [PATCH 0/6] workqueue: base pwq pool release and nr_active on the backing pool
Date: Fri, 31 Jul 2026 04:57:32 -0700	[thread overview]
Message-ID: <20260731-wq-pool-refactor-v1-0-8eaf71cdab5f@debian.org> (raw)

The goal is to unify per-cpu and unbound workqueues onto one backend, so
an unbound workqueue can run on the concurrency-managed per-cpu pools and
WQ_PERCPU just requests that backend [1]. This series is preparation and
changes no behaviour on its own.

These changes also is a reasonable readability cleanup.

What will come later:

  * Introduce a concurrency-managed per-cpu affinity scope
    (WQ_AFFN_PERCPU_CM) — percpu as an affinity setting

  * Direct pool selection (fold the create-then-convert), and rename the
    helpers that are no longer unbound-specific: install_unbound_pwq(),
    unbound_pwq(), unbound_pwq_slot() (and alloc_unbound_pwq() -> alloc_pwq()).

  * Dynamic switching between per-cpu and unbound backing for CPU isolation.

Am I on the right path?

[1] https://lore.kernel.org/all/ak569WYSm3ygKl1-@slm.duckdns.org

Signed-off-by: Breno Leitao <leitao@debian.org>
---
Breno Leitao (6):
      workqueue: factor out get_percpu_pool()
      workqueue: factor out alloc_and_link_percpu_pwqs()
      workqueue: release pwq pools by pool type
      workqueue: account nr_active by the backing pool
      workqueue: add a per-cpu backend for unbound pwqs
      workqueue: install per-cpu pwqs at creation for __WQ_PERCPU_POOLS

 include/linux/workqueue.h |   1 +
 kernel/workqueue.c        | 143 +++++++++++++++++++++++++++++++++-------------
 2 files changed, 105 insertions(+), 39 deletions(-)
---
base-commit: dbff1ec23f68640a743512e8ada125795d1b72c7
change-id: 20260729-wq-pool-refactor-0fb28721f83f

Best regards,
--  
Breno Leitao <leitao@debian.org>


             reply	other threads:[~2026-07-31 11:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 11:57 Breno Leitao [this message]
2026-07-31 11:57 ` [PATCH 1/6] workqueue: factor out get_percpu_pool() Breno Leitao
2026-07-31 11:57 ` [PATCH 2/6] workqueue: factor out alloc_and_link_percpu_pwqs() Breno Leitao
2026-07-31 11:57 ` [PATCH 3/6] workqueue: release pwq pools by pool type Breno Leitao
2026-08-03  0:31   ` Tejun Heo
2026-08-03 14:02     ` Breno Leitao
2026-08-03 16:50       ` Tejun Heo
2026-07-31 11:57 ` [PATCH 4/6] workqueue: account nr_active by the backing pool Breno Leitao
2026-08-03  0:34   ` Tejun Heo
2026-08-03 14:19     ` Breno Leitao
2026-07-31 11:57 ` [PATCH 5/6] workqueue: add a per-cpu backend for unbound pwqs Breno Leitao
2026-08-03  0:36   ` Tejun Heo
2026-08-03 16:35     ` Breno Leitao
2026-08-03 16:58       ` Tejun Heo
2026-07-31 11:57 ` [PATCH 6/6] workqueue: install per-cpu pwqs at creation for __WQ_PERCPU_POOLS Breno Leitao

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=20260731-wq-pool-refactor-v1-0-8eaf71cdab5f@debian.org \
    --to=leitao@debian.org \
    --cc=jiangshanlai@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.crivellari@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®