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>
---
 Documentation/admin-guide/cgroup-v2.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
index b26b5274eaaf..a6f58aecb431 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
 --------------------------
-- 
2.39.3

On Tue, Oct 17, 2023 at 01:13:41PM -0400, Waiman Long wrote:
> 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>

Applied to cgroup/for-6.7.

Thanks.

-- 
tejun