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 07:18:55 -1000 [thread overview]
Message-ID: <ZpAT_xu0oXjQsKM7@slm.duckdns.org> (raw)
In-Reply-To: <4e1078d6-6970-4eea-8f73-56a3815794b5@redhat.com>
Hello,
On Thu, Jul 11, 2024 at 10:05:22AM -0400, Waiman Long wrote:
> Given the fact that for_each_css() iteration is filtering out csses that are
> absent, the dying counts follow the same logic of skipping it if there is no
> dying css. That also makes it easier to identify cgroups with dying
> descendant csses as we don't need filter out entries with a 0 dying count.
> It also makes the output less verbose and let user focus more on what are
> significant.
>
> I do understand that it makes it inconsistent with the ways nr_descendants
> and nr_dying_descendants are being handled as entries with 0 count are also
> displayed. I can update the patch to display those entries with 0 dying
> subsys count if other people also think that is the better way forward.
I think it'd be better to have all the keys. There are some dynamic keys in
stat files but those are mostly for things which can come and go (e.g. block
and misc devices), so yeah, I think it'd be better to show all the keys even
when they're zero.
Also, I personally would much prefer if the same prefixes are collected
together - ie. totals first and then dying. It's just a lot easier on the
eyes that way.
nr_subsys_cpu
nr_subsys_memory
nr_subsys_io
...
nr_dying_subsys_cpu
nr_dying_subsys_memory
nr_dying_subsys_io
...
Thanks.
--
tejun
next prev parent reply other threads:[~2024-07-11 17:18 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 [this message]
2024-07-11 17:39 ` Waiman Long
2024-07-11 18:44 ` Tejun Heo
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=ZpAT_xu0oXjQsKM7@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