From: Lai Jiangshan <jiangshanlai@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, ying chen <yc1082463@gmail.com>,
Lai Jiangshan <jiangshan.ljs@antgroup.com>
Subject: [PATCH V5 0/3] workqueue: Factor the way to assign rescuer work
Date: Mon, 8 Dec 2025 21:25:16 +0800 [thread overview]
Message-ID: <20251208132520.1667697-1-jiangshanlai@gmail.com> (raw)
From: Lai Jiangshan <jiangshan.ljs@antgroup.com>
Previously, the rescuer scanned for all matching work items at once and
processed them within a single rescuer thread, which could cause one
blocking work item to stall all others.
Make the rescuer process work items one-by-one instead of slurping all
matches in a single pass using a cursor.
Changed from V4:
Control the limit and call send_mayday() in rescuer_thread(), which
makes rescuer_thread() responsible for ensuring the cursor is not left
behind.
v4: https://lore.kernel.org/lkml/20251125063617.671199-1-jiangshanlai@gmail.com/
Lai Jiangshan (3):
workqueue: Refactor send_mayday() to take pwq directly
workqueue: Process rescuer work items one-by-one using a cursor
workqueue: Process extra works in rescuer on memory pressure
kernel/workqueue.c | 119 ++++++++++++++++++++++++++++++++++-----------
1 file changed, 91 insertions(+), 28 deletions(-)
--
2.19.1.6.gb485710b
next reply other threads:[~2025-12-08 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 13:25 Lai Jiangshan [this message]
2025-12-08 13:25 ` [PATCH V5 1/3] workqueue: Make send_mayday() take a PWQ argument directly Lai Jiangshan
2025-12-08 13:25 ` [PATCH V5 2/3] workqueue: Process rescuer work items one-by-one using a cursor Lai Jiangshan
2025-12-08 13:25 ` [PATCH V5 3/3] workqueue: Process extra works in rescuer on memory pressure Lai Jiangshan
2025-12-08 19:24 ` [PATCH V5 0/3] workqueue: Factor the way to assign rescuer work 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=20251208132520.1667697-1-jiangshanlai@gmail.com \
--to=jiangshanlai@gmail.com \
--cc=jiangshan.ljs@antgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yc1082463@gmail.com \
/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®