From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Zefan Li <lizefan.x@bytedance.com>,
Jonathan Corbet <corbet@lwn.net>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kamalesh Babulal <kamalesh.babulal@oracle.com>,
Roman Gushchin <roman.gushchin@linux.dev>
Subject: Re: [PATCH v3 1/2] cgroup: Show # of subsystem CSSes in cgroup.stat
Date: Thu, 11 Jul 2024 08:44:31 -1000 [thread overview]
Message-ID: <ZpAoD7_o8bf6yVGr@slm.duckdns.org> (raw)
In-Reply-To: <76e70789-986a-44c2-bfdc-d636f425e5ae@redhat.com>
Hello,
On Thu, Jul 11, 2024 at 01:39:38PM -0400, Waiman Long wrote:
> On 7/11/24 13:18, Tejun Heo wrote:
...
> Currently, I use the for_each_css() macro for iteration. If you mean
> displaying all the possible cgroup subsystems even if they are not enabled
> for the current cgroup, I will have to manually do the iteration.
Just wrapping it with for_each_subsys() should do, no? for_each_css() won't
iterate anything if css doesn't exist for the cgroup.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-07-11 18:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 18:23 [PATCH v3 1/2] cgroup: Show # of subsystem CSSes in cgroup.stat Waiman Long
2024-07-10 18:23 ` [PATCH v3 2/2] cgroup: Limit frequency of reading cgroup.stat for unprivileged users Waiman Long
2024-07-10 21:43 ` [PATCH v3 1/2] cgroup: Show # of subsystem CSSes in cgroup.stat Roman Gushchin
2024-07-10 23:49 ` Waiman Long
2024-07-10 21:59 ` Tejun Heo
2024-07-10 23:51 ` Waiman Long
2024-07-11 13:49 ` Johannes Weiner
2024-07-11 14:05 ` Waiman Long
2024-07-11 17:18 ` Tejun Heo
2024-07-11 17:39 ` Waiman Long
2024-07-11 18:44 ` Tejun Heo [this message]
2024-07-11 18:51 ` Waiman Long
2024-07-11 18:59 ` Tejun Heo
2024-07-11 19:13 ` Waiman Long
2024-07-11 19:21 ` Tejun Heo
2024-07-11 19:29 ` Waiman Long
2024-07-11 19:59 ` Johannes Weiner
2024-07-11 21:00 ` Waiman Long
2024-07-11 21:57 ` Waiman Long
2024-07-12 16:29 ` Johannes Weiner
2024-07-12 17:10 ` Waiman Long
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=ZpAoD7_o8bf6yVGr@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=kamalesh.babulal@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=roman.gushchin@linux.dev \
/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