linux-kernel - Re: [PATCH v3] blk-throtl: optimize IOPS throttle for large IO scenarios

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 for Android: free password hash cracker in your pocket

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

Message-ID: <YRGumHUfK5sJc4A/@mtj.duckdns.org>
Date:   Mon, 9 Aug 2021 12:39:20 -1000
From:   Tejun Heo <tj@...nel.org>
To:     brookxu <brookxu.cn@...il.com>
Cc:     axboe@...nel.dk, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org, cgroups@...r.kernel.org
Subject: Re: [PATCH v3] blk-throtl: optimize IOPS throttle for large IO
 scenarios

On Mon, Aug 02, 2021 at 11:51:56AM +0800, brookxu wrote:
> From: Chunguang Xu <brookxu@...cent.com>
> 
> After patch 54efd50 (block: make generic_make_request handle
> arbitrarily sized bios), the IO through io-throttle may be larger,
> and these IOs may be further split into more small IOs. However,
> IOPS throttle does not seem to be aware of this change, which
> makes the calculation of IOPS of large IOs incomplete, resulting
> in disk-side IOPS that does not meet expectations. Maybe we should
> fix this problem.
> 
> We can reproduce it by set max_sectors_kb of disk to 128, set
> blkio.write_iops_throttle to 100, run a dd instance inside blkio
> and use iostat to watch IOPS:
> 
> dd if=/dev/zero of=/dev/sdb bs=1M count=1000 oflag=direct
> 
> As a result, without this change the average IOPS is 1995, with
> this change the IOPS is 98.
> 
> v3: Optimize the use of atomic variables.
> v2: Use atomic variables to solve synchronization problems.
> 
> Signed-off-by: Chunguang Xu <brookxu@...cent.com>

Acked-by: Tejun Heo <tj@...nel.org>

Thanks.

-- 
tejun