From: Tejun Heo <tj@kernel.org>
To: Yao Kai <yaokai34@huawei.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
Breno Leitao <leitao@debian.org>,
linux-kernel@vger.kernel.org,
liuyongqiang <liuyongqiang13@huawei.com>
Subject: Re: [QUESTION] workqueue: Reducing flush_workqueue() overhead for unbound workqueues
Date: Tue, 01 Sep 2026 11:11:58 -1000 [thread overview]
Message-ID: <92e520050991ea409925012255480655@kernel.org> (raw)
In-Reply-To: <0a030145-c108-4365-ba2d-ac1973a1e352@huawei.com>
Hello,
On Tue, Sep 01, 2026 at 04:46:06PM +0800, Yao Kai wrote:
> Is there a recommended way to avoid this overhead for such case,
> I would appreciate guidance on how this problem should be solved.
Posted a patchset which makes flush_workqueue() visit only the pwqs which
have been active since the last flush:
https://lore.kernel.org/all/20260901210929.3092513-1-tj@kernel.org/
Can you please test whether it resolves the fsync latency issue you're
seeing?
Thanks.
--
tejun
prev parent reply other threads:[~2026-09-01 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 8:46 Yao Kai
2026-09-01 21:11 ` Tejun Heo [this message]
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=92e520050991ea409925012255480655@kernel.org \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyongqiang13@huawei.com \
--cc=yaokai34@huawei.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®