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] [day] [month] [year] [list]
Message-Id: <171960811810.898565.9691388431635837442.b4-ty@kernel.dk>
Date: Fri, 28 Jun 2024 14:55:18 -0600
From: Jens Axboe <axboe@...nel.dk>
To: tj@...nel.org, josef@...icpanda.com, Yu Kuai <yukuai1@...weicloud.com>
Cc: cgroups@...r.kernel.org, linux-block@...r.kernel.org, 
 linux-kernel@...r.kernel.org, yukuai3@...wei.com, yi.zhang@...wei.com, 
 yangerkun@...wei.com
Subject: Re: [PATCH v2] blk-throttle: fix lower control under super low
 iops limit


On Tue, 18 Jun 2024 14:21:08 +0800, Yu Kuai wrote:
> User will configure allowed iops limit in 1s, and calculate_io_allowed()
> will calculate allowed iops in the slice by:
> 
> limit * HZ / throtl_slice
> 
> However, if limit is quite low, the result can be 0, then
> allowed IO in the slice is 0, this will cause missing dispatch and
> control will be lower than limit.
> 
> [...]

Applied, thanks!

[1/1] blk-throttle: fix lower control under super low iops limit
      commit: 1beabab88ecee0698ecee7b54afa9cce7046ef96

Best regards,
-- 
Jens Axboe




Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ