From: Breno Leitao <leitao@debian.org>
To: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>
Cc: marco.crivellari@suse.com, linux-kernel@vger.kernel.org,
Breno Leitao <leitao@debian.org>,
kernel-team@meta.com
Subject: [PATCH wq/for-7.4 0/2] workqueue: give percpu its own max_active and derive attrs from flags
Date: Thu, 10 Sep 2026 07:54:11 -0700 [thread overview]
Message-ID: <20260910-realsplit_last_v2-v1-0-464d64b71b29@debian.org> (raw)
Phase two of unifying the percpu and unbound workqueue paths, following
the discussion at [1].
wq->max_active means one thing on a concurrency managed per-cpu pool and
another on an unbound one. Patch 1 gives the per-cpu case its own field,
as Tejun suggested.
Patch 2 builds the standard attrs from the workqueue flags instead of
picking one of three static arrays, which leaves alloc_and_link_pwqs()
with a single apply_workqueue_attrs_locked() call for every workqueue
No visible change intented for our workqueue users.
[1] https://lore.kernel.org/all/20260714-tejun1-v1-0-024d59241386@debian.org/
Signed-off-by: Breno Leitao <leitao@debian.org>
---
Breno Leitao (2):
workqueue: give percpu workqueues their own max_active
workqueue: derive the standard attrs from the workqueue flags
kernel/workqueue.c | 120 ++++++++++++++++++++++++++---------------------------
1 file changed, 59 insertions(+), 61 deletions(-)
---
base-commit: f1639cde5f5c1bee25498ef988227ee8cf5ddb04
change-id: 20260910-realsplit_last_v2-3a73d7986db4
Best regards,
--
Breno Leitao <leitao@debian.org>
next reply other threads:[~2026-09-10 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 14:54 Breno Leitao [this message]
2026-09-10 14:54 ` [PATCH wq/for-7.4 1/2] workqueue: give percpu workqueues their own max_active Breno Leitao
2026-09-10 14:54 ` [PATCH wq/for-7.4 2/2] workqueue: derive the standard attrs from the workqueue flags Breno Leitao
2026-09-10 22:53 ` [PATCH wq/for-7.4 0/2] workqueue: give percpu its own max_active and derive attrs from flags 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=20260910-realsplit_last_v2-v1-0-464d64b71b29@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®