Linux cgroups development
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Zefan Li <lizefan.x@bytedance.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH-cgroup 1/2] cgroup: Show # of subsystem CSSes in /proc/cgroups
Date: Mon, 8 Jul 2024 15:01:39 -0400	[thread overview]
Message-ID: <b505c15b-8fd2-44f2-8e33-46ae29c2696e@redhat.com> (raw)
In-Reply-To: <Zowzvf2NEOzgXYr3@slm.duckdns.org>


On 7/8/24 14:45, Tejun Heo wrote:
> Hello, Waiman.
>
> On Fri, Jul 05, 2024 at 08:56:21PM -0400, Waiman Long wrote:
>> The /proc/cgroups file shows the number of cgroups for each of the
>> subsystems.  With cgroup v1, the number of CSSes is the same as the
>> number of cgroups. That is not the case anymore with cgroup v2. The
>> /proc/cgroups file cannot show the actual number of CSSes for the
>> subsystems that are bound to cgroup v2.
>>
>> So if a v2 cgroup subsystem is leaking cgroups (typically memory
>> cgroup), we can't tell by looking at /proc/cgroups which cgroup
>> subsystems may be responsible.  This patch adds a css counter in the
>> cgroup_subsys structure to keep track of the number of CSSes for each
>> of the cgroup subsystems.
> The count sounds useful to me but can we add it in cgroup.stats instead?

That information is certainly useful to display to cgroup.stat which 
currently only shows nr_descendants and nr_dying_descendants. So does 
"nr_<subsys_name> <cnt>" for each cgroup subsystems look good to you or 
do you have other suggestion?

The reason for this patch is because I got a bug report about leaking 
blkio cgroup due to the information shown in /proc/cgroups. I know you 
want do deprecate it for cgroup v2. How about adding a iine like "# 
Deprecated for cgroup v2, use cgroup.stats file for cgroup counts" at 
the top of /proc/cgroups when cgroup v2 is active?

Cheers,
Longman



  reply	other threads:[~2024-07-08 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-06  0:56 [PATCH-cgroup 1/2] cgroup: Show # of subsystem CSSes in /proc/cgroups Waiman Long
2024-07-06  0:56 ` [PATCH-cgroup 2/2] cgroup: Remove nr_cgrps Waiman Long
2024-07-08 18:45 ` [PATCH-cgroup 1/2] cgroup: Show # of subsystem CSSes in /proc/cgroups Tejun Heo
2024-07-08 19:01   ` Waiman Long [this message]
2024-07-08 19:05     ` Tejun Heo
2024-07-08 19:18       ` 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=b505c15b-8fd2-44f2-8e33-46ae29c2696e@redhat.com \
    --to=longman@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.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