aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorWaiman Long <longman@redhat.com>2023-10-17 13:13:41 -0400
committerTejun Heo <tj@kernel.org>2023-10-17 22:45:44 -1000
commita41796b5537dd90eed0e8a6341dec97f4507f5ed (patch)
treebe54633e675dac2f32055bd00f78e73858195431
parentcgroup: use legacy_name for cgroup v1 disable info (diff)
downloadwireguard-linux-a41796b5537dd90eed0e8a6341dec97f4507f5ed.tar.xz
wireguard-linux-a41796b5537dd90eed0e8a6341dec97f4507f5ed.zip
docs/cgroup: Add the list of threaded controllers to cgroup-v2.rst
The cgroup-v2 file mentions the concept of threaded controllers which can be used in a threaded cgroup. However, it doesn't mention clearly which controllers are threaded leading to some confusion about what controller can be used requiring some experimentation. Clear this up by explicitly listing the controllers that can be used currently in a threaded cgroup. Signed-off-by: Waiman Long <longman@redhat.com> Signed-off-by: Tejun Heo <tj@kernel.org>
-rw-r--r--Documentation/admin-guide/cgroup-v2.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
index e40b8560e002..e440aee4fe94 100644
--- a/Documentation/admin-guide/cgroup-v2.rst
+++ b/Documentation/admin-guide/cgroup-v2.rst
@@ -364,6 +364,13 @@ constraint, a threaded controller must be able to handle competition
between threads in a non-leaf cgroup and its child cgroups. Each
threaded controller defines how such competitions are handled.
+Currently, the following controllers are threaded and can be enabled
+in a threaded cgroup::
+
+- cpu
+- cpuset
+- perf_event
+- pids
[Un]populated Notification
--------------------------