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.3
Date: Mon, 17 Aug 2026 11:49:19 -1000 [thread overview]
Message-ID: <f2d890e7272c68054a395c57c08fcfee@kernel.org> (raw)
Hello,
The following changes since commit f0e6f20cb52b14c2c441f04e21cef0c95d498cac:
Merge tag 'ntfs3_for_7.2' of https://github.com/Paragon-Software-Group/linux-ntfs3 (2026-06-24 10:05:53 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git tags/wq-for-7.3
for you to fetch changes up to 20a80e7f6b71bd664c98e95589f0cbc68804d200:
workqueue: annotate racy p->wake_cpu accesses in kick_pool_pick() (2026-08-13 07:00:19 -1000)
----------------------------------------------------------------
workqueue: Changes for v7.3
- Worker wakeups moved out of pool->lock on the hot paths, shortening lock
hold times. The wakeup can be expensive on arm64 due to the idle wakeup
IPI, and the change improves the workqueue microbenchmark there by up to
10%.
- Stall diagnostics now report pools stuck with no running worker, with a
backtrace of what the CPU is executing and the likely culprit worker,
instead of dumping every in-flight worker.
- Preparation for turning per-cpu workqueues into an affinity scope of
unbound workqueues instead of a separate backend.
- Race annotations for KCSAN and sparse warnings, and doc and monitoring
script fixes.
----------------------------------------------------------------
Breno Leitao (21):
workqueue: split kick_pool() into kick_pool_pick()
workqueue: defer the worker wakeup outside pool->lock in __queue_work()
workqueue: defer the worker wakeup outside pool->lock in process_one_work()
workqueue: only show running workers in stall diagnostics
workqueue: trigger a single-CPU backtrace for stalled pools
workqueue: dump the last woken worker for stalled pools
workqueue: annotate racy PWQ_STAT_CPU_TIME update in wq_worker_tick()
workqueue: annotate racy sum_exec_runtime reads for CPU-intensive detection
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: test WQ_UNBOUND explicitly in the hotplug loops
workqueue: rename wq->unbound_attrs to wq->attrs
workqueue: allocate attrs for all workqueues
workqueue: rename alloc_unbound_pwq() to alloc_pwq()
workqueue: skip the node_nr_active update for non-unbound workqueues
workqueue: use rcu_dereference_sched() in workqueue_congested()
workqueue: use RCU accessors when populating wq->cpu_pwq
workqueue: BUG_ON() instead of returning NULL in wq_node_nr_active()
workqueue: annotate racy p->wake_cpu accesses in kick_pool_pick()
Manuel Ebner (1):
docs: workqueue: Fix bracket
Yousef Alhouseen (1):
tools/workqueue: parse help before importing drgn
Documentation/core-api/workqueue.rst | 2 +-
kernel/workqueue.c | 323 ++++++++++++++++++++++++-----------
tools/workqueue/wq_dump.py | 16 +-
tools/workqueue/wq_monitor.py | 6 +-
4 files changed, 240 insertions(+), 107 deletions(-)
--
tejun
reply other threads:[~2026-08-17 21:49 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=f2d890e7272c68054a395c57c08fcfee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.