Linux block layer
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Tao Cui <cui.tao@linux.dev>
Cc: hannes@cmpxchg.org, mkoutny@suse.com, corbet@lwn.net,
	skhan@linuxfoundation.org, josef@toxicpanda.com, axboe@kernel.dk,
	cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	cuitao@kylinos.cn
Subject: Re: [PATCH v4] Docs/admin-guide/cgroup-v2: document io.latency rotational vs non-rotational behavior
Date: Sun, 02 Aug 2026 11:32:49 -1000	[thread overview]
Message-ID: <14bd63f0e59ce815ec1a1d066f578aa0@kernel.org> (raw)
In-Reply-To: <20260728095707.2398498-1-cui.tao@linux.dev>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]

On Tue, Jul 28, 2026 at 05:57:07PM +0800, Tao Cui wrote:
> io.latency is documented only in terms of average latency and the avg_lat
> stat, which matches rotational devices.  On non-rotational devices a group
> misses its target once enough of the IOs in the window individually exceed
> it, and io.stat reports missed/total rather than avg_lat/win.
>
> Describe both cases: how a miss is detected, note that the avg_lat tuning
> guidance is rotational-only, and update the io.stat field list (mark
> avg_lat/win as rotational-only, document missed/total).
>
> Acked-by: Michal Koutný <mkoutny@suse.com>
> Signed-off-by: Tao Cui <cuitao@kylinos.cn>

Applied to cgroup/for-7.2-fixes.

Thanks.

--
tejun

      reply	other threads:[~2026-08-02 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  9:57 [PATCH v4] Docs/admin-guide/cgroup-v2: document io.latency rotational vs non-rotational behavior Tao Cui
2026-08-02 21:32 ` Tejun Heo [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=14bd63f0e59ce815ec1a1d066f578aa0@kernel.org \
    --to=tj@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=cui.tao@linux.dev \
    --cc=cuitao@kylinos.cn \
    --cc=hannes@cmpxchg.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=skhan@linuxfoundation.org \
    /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