linux-kernel - Re: very low IOPS due to "block: reduce kblockd_mod_delayed_work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 23 Dec 2021 03:50:23 -0800
From:   Christoph Hellwig <hch@...radead.org>
To:     Jens Axboe <axboe@...nel.dk>
Cc:     "Alex Xu (Hello71)" <alex_y_xu@...oo.ca>,
        linux-block@...r.kernel.org, Dexuan Cui <decui@...rosoft.com>,
        ming.lei@...hat.com, hch@....de, Long Li <longli@...rosoft.com>,
        "Michael Kelley (LINUX)" <mikelley@...rosoft.com>,
        linux-kernel@...r.kernel.org
Subject: Re: very low IOPS due to "block: reduce
 kblockd_mod_delayed_work_on() CPU consumption"

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.