public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Tejun Heo <tj@kernel.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: Wed, 4 Mar 2026 09:11:47 -0800	[thread overview]
Message-ID: <aahnjjOP_5Qzfa0K@gmail.com> (raw)
In-Reply-To: <aahiUfIRh84tpqrw@slm.duckdns.org>

On Wed, Mar 04, 2026 at 06:48:17AM -1000, Tejun Heo wrote:
> Hello, Breno.
> 
> On Wed, Mar 04, 2026 at 01:56:43AM -0800, Breno Leitao wrote:
> > > 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.
> > 
> > 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.
> 
> This is a pretty trivial patch to carry, right? Or just do it as a part of
> boot system config?

Yes, a very trivial one, but, which requires some work to be done at
every rebase. Mainly when trying to use pristine stable trees.

> > > What's the benefit of exposing these extra numbers which
> > > probably don't mean much for most people?
> > 
> > My original plan was to introduce a Kconfig option for this. In v1 (about a
> > month ago), Michal suggested removing the toggle entirely and always exposing
> > the stats, which seemed reasonable to me and received no objections, so I
> > went ahead with that approach.
> > 
> > To be clear: is your position that we should not support building a kernel
> > that always exposes the detailed stats in io.stat?
> 
> As a debug option maybe but I'd prefer if vendors (including us) that want
> to permanently enable these debug stats carried the patch in their trees.

That is fair, thanks for the direction!
--breno


  reply	other threads:[~2026-03-04 17:11 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 [this message]
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=aahnjjOP_5Qzfa0K@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox