summaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/inotify.txt
diff options
context:
space:
mode:
authorRoman Gushchin <guro@fb.com>2017-07-28 18:28:44 +0100
committerTejun Heo <tj@kernel.org>2017-08-02 12:05:20 -0700
commit1a926e0bbab83bae8207d05a533173425e0496d1 (patch)
tree8b0d77250135e254907205b4711e7a7b7174b78e /Documentation/filesystems/inotify.txt
parent0679dee03c6d706d57145ea92c23d08fa10a1999 (diff)
downloadop-kernel-dev-1a926e0bbab83bae8207d05a533173425e0496d1.zip
op-kernel-dev-1a926e0bbab83bae8207d05a533173425e0496d1.tar.gz
cgroup: implement hierarchy limits
Creating cgroup hierearchies of unreasonable size can affect overall system performance. A user might want to limit the size of cgroup hierarchy. This is especially important if a user is delegating some cgroup sub-tree. To address this issue, introduce an ability to control the size of cgroup hierarchy. The cgroup.max.descendants control file allows to set the maximum allowed number of descendant cgroups. The cgroup.max.depth file controls the maximum depth of the cgroup tree. Both are single value r/w files, with "max" default value. The control files exist on each hierarchy level (including root). When a new cgroup is created, we check the total descendants and depth limits on each level, and if none of them are exceeded, a new cgroup is created. Only alive cgroups are counted, removed (dying) cgroups are ignored. Signed-off-by: Roman Gushchin <guro@fb.com> Suggested-by: Tejun Heo <tj@kernel.org> Signed-off-by: Tejun Heo <tj@kernel.org> Cc: Zefan Li <lizefan@huawei.com> Cc: Waiman Long <longman@redhat.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: kernel-team@fb.com Cc: cgroups@vger.kernel.org Cc: linux-doc@vger.kernel.org Cc: linux-kernel@vger.kernel.org
Diffstat (limited to 'Documentation/filesystems/inotify.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud