summaryrefslogtreecommitdiffstats
path: root/init/Kconfig
diff options
context:
space:
mode:
authorParav Pandit <pandit.parav@gmail.com>2016-03-05 07:00:56 +0100
committerTejun Heo <tj@kernel.org>2016-03-05 13:48:01 +0100
commit6cc578df40bd60b791725e4451bc01f8c80abd8b (patch)
treed6eca8be124dfab0c70249e1302f19987beea9d4 /init/Kconfig
parentcgroup: remove stale item in cgroup-v1 document INDEX file. (diff)
downloadlinux-6cc578df40bd60b791725e4451bc01f8c80abd8b.tar.xz
linux-6cc578df40bd60b791725e4451bc01f8c80abd8b.zip
cgroup: Trivial correction to reflect controller.
Trivial correction in menuconfig help to reflect PIDs as controller instead of subsystem to align to rest of the text and documentation. Signed-off-by: Parav Pandit <pandit.parav@gmail.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'init/Kconfig')
-rw-r--r--init/Kconfig4
1 files changed, 2 insertions, 2 deletions
diff --git a/init/Kconfig b/init/Kconfig
index 22320804fbaf..9fefb8e40541 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1047,10 +1047,10 @@ config CGROUP_PIDS
is fairly trivial to reach PID exhaustion before you reach even a
conservative kmemcg limit. As a result, it is possible to grind a
system to halt without being limited by other cgroup policies. The
- PIDs cgroup subsystem is designed to stop this from happening.
+ PIDs controller is designed to stop this from happening.
It should be noted that organisational operations (such as attaching
- to a cgroup hierarchy will *not* be blocked by the PIDs subsystem),
+ to a cgroup hierarchy will *not* be blocked by the PIDs controller),
since the PIDs limit only affects a process's ability to fork, not to
attach to a cgroup.