From: Tejun Heo <tj@kernel.org>
To: Peng Yu <yupeng0921@gmail.com>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Chaitanya Kulkarni" <kch@nvidia.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Josef Bacik" <josef@toxicpanda.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Maurizio Lombardi" <mlombard@arkamax.eu>,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/2] cgroup: track the effective css in each cgroup
Date: Thu, 01 Oct 2026 07:56:28 -1000 [thread overview]
Message-ID: <aa7f5ccd9fc7a7770336a48f458fee19@kernel.org> (raw)
In-Reply-To: <20260929232411.101087-2-yupeng0921@gmail.com>
On Tue, Sep 29, 2026 at 04:24:10PM -0700, Peng Yu wrote:
> cgroup_e_css() and cgroup_get_e_css() find the effective css by walking
> up the hierarchy until they reach a cgroup that has the subsystem
> enabled. Per-I/O users such as nvmet need this lookup to be O(1).
>
> Track the effective css in each cgroup and make cgroup_e_css() and
> cgroup_get_e_css() use it. When a css is brought online or offline,
> update the effective css of its cgroup and of all descendants.
Applied to cgroup/for-7.4 with the subject capitalized.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-10-01 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 23:24 [PATCH v7 0/2] nvmet: add cgroup_id to charge namespace I/O to a cgroup Peng Yu
2026-09-29 23:24 ` [PATCH v7 1/2] cgroup: track the effective css in each cgroup Peng Yu
2026-10-01 17:56 ` Tejun Heo [this message]
2026-09-29 23:24 ` [PATCH v7 2/2] nvmet: add cgroup_id to charge namespace I/O to a cgroup Peng Yu
2026-10-01 18:10 ` 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=aa7f5ccd9fc7a7770336a48f458fee19@kernel.org \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mkoutny@suse.com \
--cc=mlombard@arkamax.eu \
--cc=sagi@grimberg.me \
--cc=yupeng0921@gmail.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
all inboxes | Powered by JetHome®