From: Breno Leitao <leitao@debian.org>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Tejun Heo <tj@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Josef Bacik <josef@toxicpanda.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, thevlad@meta.com, kernel-team@meta.com
Subject: Re: [PATCH v2] blk-cgroup: always display debug stats in io.stat
Date: Wed, 4 Mar 2026 05:48:52 -0800 [thread overview]
Message-ID: <aag30EagagRlie0A@gmail.com> (raw)
In-Reply-To: <poawwl44nvy4ru4mmjqi3kxfq7xqcpdeq6ghixphcrwhpv3bnz@xsltjt52rbqm>
Hello Michal,
On Wed, Mar 04, 2026 at 02:28:03PM +0100, Michal Koutný wrote:
>
> On Wed, Mar 04, 2026 at 01:56:43AM -0800, Breno Leitao <leitao@debian.org> wrote:
> > My goal is to ship a kernel that exposes these detailed io stats by
> > default, without requiring any runtime configuration. The stats should
> > simply be available out of the box.
>
> Does it mean the information is useful to you since early boot and
> adjusting the param with a userspace tool in boot sequence is too late?
Not exactly. The goal is to have a kernel binary that, regardless of
where it is deployed and how it is configured, I know know it provides
full io.stat details without requiring any tunable to be changed.
next prev parent reply other threads:[~2026-03-04 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 14:11 [PATCH v2] blk-cgroup: always display debug stats in io.stat Breno Leitao
2026-03-03 17:46 ` Tejun Heo
2026-03-04 9:56 ` Breno Leitao
2026-03-04 16:48 ` Tejun Heo
2026-03-04 17:11 ` Breno Leitao
2026-03-04 13:28 ` Michal Koutný
2026-03-04 13:48 ` Breno Leitao [this message]
2026-03-04 16:42 ` Tejun Heo
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=aag30EagagRlie0A@gmail.com \
--to=leitao@debian.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=thevlad@meta.com \
--cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.