aboutsummaryrefslogtreecommitdiffstats
path: root/man7/cgroups.7
diff options
context:
space:
mode:
Diffstat (limited to 'man7/cgroups.7')
-rw-r--r--man7/cgroups.717
1 files changed, 17 insertions, 0 deletions
diff --git a/man7/cgroups.7 b/man7/cgroups.7
index e95a4cd026..a173e85c09 100644
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -1109,6 +1109,23 @@ The requirement to write
.IR """threaded"""
to each of these cgroups is somewhat cumbersome,
but allows for possible future extensions to the thread-mode model.
+.\" FIXME
+.\" Re the preceding paragraphs... Are there other reasosn for the
+.\" (cumbersome) requirement to write 'threaded' to each of the
+.\" cgroup.type files in the threaded subtrees? Tejun Heo mentioned
+.\" the following:
+.\"
+.\" Consistency w/ the cgroups right under the root
+.\" cgroup. Because they can be both domains and
+.\" threadroots, we can't switch the children over
+.\" to thread mode automatically. Doing that for
+.\" cgroups further down in the hierarchy would be
+.\" really inconsistent.
+.\"
+.\" But, it's not clear to me how "Doing that for cgroups
+.\" further down in the hierarchy would be really inconsistent",
+.\" since in the current implementation, those same thread groups
+.\" are converted to "domain invalid" type. What am I missing?
.PP
The second way of creating a threaded subtree is as follows:
.IP 1. 3