public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Gushchin <guro@fb.com>
To: Waiman Long <longman@redhat.com>
Cc: <cgroups@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
	Zefan Li <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>, <kernel-team@fb.com>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cgroup: add cgroup.stat interface with basic hierarchy stats
Date: Thu, 27 Jul 2017 18:46:13 +0100	[thread overview]
Message-ID: <20170727174613.GA6457@castle.DHCP.thefacebook.com> (raw)
In-Reply-To: <6a72e074-e01f-b93f-2c03-2bd0366d005b@redhat.com>

On Thu, Jul 27, 2017 at 01:38:55PM -0400, Waiman Long wrote:
> On 07/27/2017 12:14 PM, Roman Gushchin wrote:
> > Add a cgroup.stat interface to the base cgroup control files
> > with the following metrics:
> >
> > nr_descendants		total number of descendant cgroups
> > nr_dying_descendants	total number of dying descendant cgroups
> > max_descendant_depth	maximum descent depth below the current cgroup
> 
> Both nr_descendants and max_descendant_depth can be found easily from
> userspace by scanning the cgroup directory. nr_dying_descendants is a
> transient figure and it should be 0 most of the time. So I wonder how
> useful it can be.
> 
> This new interface file will be more useful if it can reveal information
> that cannot be easily obtained by looking from userspace alone.

A cgroup can be in dying state for substantional amount of time
(imagine a memcg which holds a page mlocked by a process in an other cgroup).

The total amount of cgroups, as well as tree depth include dying cgroups,
which are not visible from the userspace.

The main purpose of this interface is to have a reasonable way to check if
there are no leaks/refcounting issues, which prevents cgroups from being
completely freed.

Thanks!

Roman

  reply	other threads:[~2017-07-27 17:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 16:14 [PATCH] cgroup: add cgroup.stat interface with basic hierarchy stats Roman Gushchin
2017-07-27 16:22 ` Tejun Heo
2017-07-28 13:01   ` Roman Gushchin
2017-07-28 15:09     ` Tejun Heo
2017-07-27 17:38 ` Waiman Long
2017-07-27 17:46   ` Roman Gushchin [this message]
2017-07-27 17:55     ` 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=20170727174613.GA6457@castle.DHCP.thefacebook.com \
    --to=guro@fb.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@fb.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=longman@redhat.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