From: Yin Fengwei <fengwei.yin@intel.com>
To: Dexuan Cui <decui@microsoft.com>, Jens Axboe <axboe@kernel.dk>,
"Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"hch@lst.de" <hch@lst.de>, Long Li <longli@microsoft.com>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Sang, Oliver" <oliver.sang@intel.com>,
"Li, Philip" <philip.li@intel.com>
Subject: Re: RE: very low IOPS due to "block: reduce kblockd_mod_delayed_work_on() CPU consumption"
Date: Tue, 28 Dec 2021 10:30:43 +0800 [thread overview]
Message-ID: <27973649-193d-a485-1ca7-983a53c7cf78@intel.com> (raw)
In-Reply-To: <BYAPR21MB127067C16809209C019BC83BBF7B9@BYAPR21MB1270.namprd21.prod.outlook.com>
Hi Jens, Dexuan,
On 12/20/2021 1:15 PM, Dexuan Cui wrote:
>> From: Jens Axboe <axboe@kernel.dk>
>> Sent: Sunday, December 19, 2021 7:28 AM
>>> ...
>>> 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...
>> ...
>> Jens Axboe
>
> Hi Jens, sorry -- unluckily I lost the test environment.. :-(
> I pinged the user to set up the test environment again, but he's
> on vacation till the beginning of January.
We hit this issue in our testing env also and will help to verify
your fixing patch. Thanks.
Regards
Yin, Fengwei
next prev parent reply other threads:[~2021-12-28 2:31 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 [this message]
[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
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=27973649-193d-a485-1ca7-983a53c7cf78@intel.com \
--to=fengwei.yin@intel.com \
--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 \
--cc=oliver.sang@intel.com \
--cc=philip.li@intel.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