mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Gushchin <guro@fb.com>
To: Tejun Heo <tj@kernel.org>
Cc: Zefan Li <lizefan@huawei.com>, Waiman Long <longman@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>, <kernel-team@fb.com>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [RFC 0/4] cgroup hierarchy controls and stats
Date: Wed, 2 Aug 2017 19:39:40 +0100	[thread overview]
Message-ID: <20170802183940.GA5590@castle.dhcp.TheFacebook.com> (raw)

Date: Wed,  2 Aug 2017 17:55:28 +0100
From: Roman Gushchin <guro@fb.com>
To: cgroups@vger.kernel.org
Cc: Roman Gushchin <guro@fb.com>
Subject: [RFC 0/4] cgroup hierarchy controls and stats
X-Mailer: git-send-email 2.13.3

Creating cgroup hierearchies of an unreasonable size can affect
system performance. A user might want to limit the size
of the cgroup hierarchy.

This patchset implements an ability to control and monitor cgroup
hierarchy size.

Patch 1 implements tracking of live and dying descendant cgroups
        on each cgroup level.
Patch 2 adds cgroup.max.descendants and cgroup.max.depth interfaces
        to set up hierarchy limits.
Patch 3 adds cgroup.stat interface with simple hierarchy stats.
Patch 4 is a trivial cleanup.

Roman Gushchin (4):
  cgroup: keep track of number of descent cgroups
  cgroup: implement hierarchy limits
  cgroup: add cgroup.stat interface with basic hierarchy stats
  cgroup: re-use the parent pointer in cgroup_destroy_locked()

 Documentation/cgroup-v2.txt |  32 +++++++++
 include/linux/cgroup-defs.h |  13 ++++
 kernel/cgroup/cgroup.c      | 163 +++++++++++++++++++++++++++++++++++++++++++-
 3 files changed, 205 insertions(+), 3 deletions(-)

--
2.13.3

                 reply	other threads:[~2017-08-02 18:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170802183940.GA5590@castle.dhcp.TheFacebook.com \
    --to=guro@fb.com \
    --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

all inboxes | Powered by JetHome®