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] [day] [month] [year] [list]
Message-ID: <874inn2uil.fsf@trenco.lwn.net>
Date: Wed, 11 Feb 2026 08:02:26 -0700
From: Jonathan Corbet <corbet@....net>
To: Tang Yizhou <yizhou.tang@...pee.com>
Cc: tj@...nel.org, axboe@...nel.dk, hch@....de, cgroups@...r.kernel.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, mkoutny@...e.com
Subject: Re: [PATCH] docs: Fix blk-iolatency peer throttling description

Tang Yizhou <yizhou.tang@...pee.com> writes:

> On Tue, Jan 20, 2026 at 9:37 PM Michal Koutný <mkoutny@...e.com> wrote:
>>
>> On Wed, Jan 14, 2026 at 07:08:37PM +0800, Tang Yizhou <yizhou.tang@...pee.com> wrote:
>> > From: Tang Yizhou <yizhou.tang@...pee.com>
>> >
>> > The current text states that peers with a lower latency target are
>> > throttled, which is the opposite of the actual behavior. In fact,
>> > blk-iolatency throttles peer groups with a higher latency target in order
>> > to protect the more latency-sensitive group.
>> >
>> > In addition, peer groups without a configured latency target are also
>> > throttled, as they are treated as lower priority compared to groups with
>> > explicit latency requirements.
>> >
>> > Update the documentation to reflect the correct throttling behavior.
>> >
>> > Signed-off-by: Tang Yizhou <yizhou.tang@...pee.com>
>> > ---
>> >  Documentation/admin-guide/cgroup-v2.rst | 10 ++++++----
>> >  1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> Not a big deal but it could've been confusing.
>>
>>
>> Acked-by: Michal Koutný <mkoutny@...e.com>
>
> Hi Jon, just checking in, do you think this patch is ready to be merged?

Tejun usually takes cgroup-related docs changes directly, so I was
deferring on this one.  If the preference is for it to go through the
docs tree I can certainly pick it up.

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ