From: Jonathan Corbet <corbet@lwn.net>
To: Tang Yizhou <yizhou.tang@shopee.com>
Cc: tj@kernel.org, axboe@kernel.dk, hch@lst.de,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, mkoutny@suse.com
Subject: Re: [PATCH] docs: Fix blk-iolatency peer throttling description
Date: Wed, 11 Feb 2026 08:02:26 -0700 [thread overview]
Message-ID: <874inn2uil.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CACuPKxnY0Uo6RU5Cw2_fS=hQcjUBwiA+G3U-LUaviVYyf0Pojw@mail.gmail.com>
Tang Yizhou <yizhou.tang@shopee.com> writes:
> On Tue, Jan 20, 2026 at 9:37 PM Michal Koutný <mkoutny@suse.com> wrote:
>>
>> On Wed, Jan 14, 2026 at 07:08:37PM +0800, Tang Yizhou <yizhou.tang@shopee.com> wrote:
>> > From: Tang Yizhou <yizhou.tang@shopee.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@shopee.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@suse.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
prev parent reply other threads:[~2026-02-11 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 11:08 [PATCH] docs: Fix blk-iolatency peer throttling description Tang Yizhou
2026-01-20 13:37 ` Michal Koutný
2026-02-11 14:50 ` Tang Yizhou
2026-02-11 15:02 ` Jonathan Corbet [this message]
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=874inn2uil.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=tj@kernel.org \
--cc=yizhou.tang@shopee.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