From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>,
linux-block@vger.kernel.org, Dexuan Cui <decui@microsoft.com>,
ming.lei@redhat.com, hch@lst.de, Long Li <longli@microsoft.com>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>,
linux-kernel@vger.kernel.org
Subject: Re: very low IOPS due to "block: reduce kblockd_mod_delayed_work_on() CPU consumption"
Date: Thu, 23 Dec 2021 03:50:23 -0800 [thread overview]
Message-ID: <YcRif3u3GxUdP3il@infradead.org> (raw)
In-Reply-To: <237bd7d8-9e75-01b5-ebe7-8b1eb747474b@kernel.dk>
On Sun, Dec 19, 2021 at 08:28:18AM -0700, Jens Axboe wrote:
> >
> > Dexuan, can you test this for your test case too? I'm going to queue
> > up a revert for -rc6 just in case.
>
> This one should be better...
We might just want something like a revert of
9f993737906b30d7b2454a38637d1f70ffd60f2f.
Or just always use a normal work queue for run_work, and then use a
timer to schedule it for the relatively rare delayed case.
prev parent reply other threads:[~2021-12-23 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1639853092.524jxfaem2.none.ref@localhost>
2021-12-18 18:57 ` very low IOPS due to "block: reduce kblockd_mod_delayed_work_on() CPU consumption" Alex Xu (Hello71)
2021-12-18 19:02 ` Jens Axboe
2021-12-19 14:58 ` Jens Axboe
2021-12-19 15:28 ` Jens Axboe
2021-12-20 5:15 ` Dexuan Cui
2021-12-28 2:30 ` Yin Fengwei
[not found] ` <20211228134926.GA31268@xsang-OptiPlex-9020>
2022-01-22 6:14 ` Dexuan Cui
2022-02-08 18:34 ` Dexuan Cui
2021-12-23 11:50 ` Christoph Hellwig [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=YcRif3u3GxUdP3il@infradead.org \
--to=hch@infradead.org \
--cc=alex_y_xu@yahoo.ca \
--cc=axboe@kernel.dk \
--cc=decui@microsoft.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=ming.lei@redhat.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