All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Breno Leitao <leitao@debian.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 06:42:32 -1000	[thread overview]
Message-ID: <aahg-PreSQLlNq2p@slm.duckdns.org> (raw)
In-Reply-To: <poawwl44nvy4ru4mmjqi3kxfq7xqcpdeq6ghixphcrwhpv3bnz@xsltjt52rbqm>

Hello,

On Wed, Mar 04, 2026 at 02:28:03PM +0100, Michal Koutný wrote:
> On Tue, Mar 03, 2026 at 07:46:46AM -1000, Tejun Heo <tj@kernel.org> wrote:
> > > 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.
> 
> Yeah, it works but BLK_CGROUP is not a module/built-in it's config
> option affecting builds. I find the module_param() in blk-cgroup.c to be
> a residual, I admit it's convenient way how to expose a tunable to
> userspace.
> 
> (Contemporary way of implementing the option could also be a cgroupfs
> mount option/feature or maybe sysctl for which tooling is available.)

I don't konw whether I'm the only one doing it but I use moduleparams as an
easy way to get non-API boot and runtime toggles whether the target code is
actually module or not. It's easy to use and the params are in a pretty gray
area in terms of API stability, so if you wanna throw in a debug option, it
works.

Thanks.

-- 
tejun

      parent reply	other threads:[~2026-03-04 16:42 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
2026-03-04 16:42     ` 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=aahg-PreSQLlNq2p@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 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.