From: Tejun Heo <tj@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: "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,
"Michal Koutný" <mkoutny@suse.com>
Subject: Re: [PATCH v2] blk-cgroup: always display debug stats in io.stat
Date: Tue, 3 Mar 2026 07:46:46 -1000 [thread overview]
Message-ID: <aacehv3rpO9irhEG@slm.duckdns.org> (raw)
In-Reply-To: <20260303-blk_cgroup_debug_stats-v2-1-196c713cb762@debian.org>
Hello,
On Tue, Mar 03, 2026 at 06:11:15AM -0800, Breno Leitao wrote:
> Remove the blkcg_debug_stats toggle and always display detailed
> statistics in the cgroup io.stat file. This includes use_delay and
> delay_nsec information, cost.wait/cost.indebt/cost.indelay for iocost,
> and latency statistics for iolatency.
>
> The stats are already being collected regardless of the toggle, so
> gating their display provides no real benefit. Additionally, blk-cgroup
The reason for gating is that these are more internal implementation details
and might change in the future.
> has not been modularized since commit 32e380aedc3de ("blkcg: make
> CONFIG_BLK_CGROUP bool"), making the module parameter a historical
> artifact. Readers of the nested-keys format should be able to handle
> additional fields.
I'm not sure what the above para means. Module param works just fine for
built-in modules on both boot command line and through sysfs.
> Before (without blkcg_debug_stats enabled):
> 253:0 rbytes=6273024 wbytes=0 rios=20 wios=0 dbytes=0 dios=0 cost.usage=0
>
> After:
> 253:0 rbytes=6273024 wbytes=0 rios=20 wios=0 dbytes=0 dios=0 cost.usage=0 cost.wait=0 cost.indebt=0 cost.indelay=0
Given that they haven't changed for a long time, maybe it's okay to expose
them by default, but why? This is something which can be toggled on easily
at any time. What's the benefit of exposing these extra numbers which
probably don't mean much for most people?
Thanks.
--
tejun
next prev parent reply other threads:[~2026-03-03 17:46 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 [this message]
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
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=aacehv3rpO9irhEG@slm.duckdns.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=thevlad@meta.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