From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] workqueue: Changes for v7.4
Date: Mon, 19 Oct 2026 06:19:26 -1000 [thread overview]
Message-ID: <d4910dda3c8d655e1a8ccaeef64662e9@kernel.org> (raw)
Hello,
The following changes since commit 93e257938aa67a6c957217db94091d9d9e5d403f:
tools/workqueue/wq_dump.py: Support backward compatibility for wq->attrs rename (2026-08-31 10:17:08 -1000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git tags/wq-for-7.4
for you to fetch changes up to bda345b3fc59f2899c50379c64a0734a3e720683:
workqueue: mark pool->nr_running as __data_racy (2026-10-14 07:03:54 -1000)
----------------------------------------------------------------
workqueue: Changes for v7.4
- Flushing a workqueue now visits only the queues used since the last flush
instead of one per possible CPU. Idle flushes get 10 to 100 times faster
on large machines, which XFS hits on every log force.
- Per-cpu workqueues are built through the same attribute path as unbound
ones and get a max_active of their own, continuing the work to turn them
into an affinity scope of unbound workqueues.
- New tracepoints for work items turning CPU-intensive, rescuer mayday and
rescue events, and BH workers yielding with work pending.
- A KCSAN annotation and small cleanups.
----------------------------------------------------------------
Aaron Tomlin (3):
workqueue: Add workqueue_cpu_intensive tracepoint
workqueue: Add workqueue_mayday and workqueue_rescued tracepoints
workqueue: Add workqueue_bh_budget_yield tracepoint
Breno Leitao (8):
workqueue: move the unbound-only attrs check to apply_workqueue_attrs()
workqueue: resolve the backing pool in alloc_pwq()
workqueue: make the default pwq optional
workqueue: build percpu pwqs through the attrs path
workqueue: rename the pwq slot helpers shared with percpu
workqueue: Give percpu workqueues their own max_active
workqueue: Derive the standard attrs from the workqueue flags
workqueue: BUG_ON() a pwq release before workqueue_init()
Hemanth Selam (1):
workqueue: Fix typo "upto" in comment
Nguyen Ngoc Thang (1):
workqueue: mark pool->nr_running as __data_racy
Tejun Heo (3):
workqueue: Add for_each_node_with_fallback()
workqueue: Maintain pwq->total_in_flight
workqueue: Make flush_workqueue() visit only pwqs active since the last flush
include/trace/events/workqueue.h | 146 ++++++++++
kernel/workqueue.c | 593 ++++++++++++++++++++++++++-------------
2 files changed, 542 insertions(+), 197 deletions(-)
--
tejun
reply other threads:[~2026-10-19 16:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d4910dda3c8d655e1a8ccaeef64662e9@kernel.org \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®