This avoids the need to decide how to partition resources between
processes which are members of cgroup A and processes in child cgroups of A.
-Note: in the upcoming unified hierarchy, a new restriction is imposed such
-that processes may reside only in leaf cgroups.
For instance, if cgroup
.I /cg1/cg2
exists, then a process may reside in
.IR /cg1/cg2 ,
but not in
.IR /cg1 .
-This is to avoid the current ambiguity in the delegation of resources
-between processes in
+This is to avoid an ambiguity cgroups v1
+with respect to the delegation of resources between processes in
.I /cg1
and its child cgroups.
-The recommended workaround is to create a subdirectory called
+The recommended approach in cgroups v2 is to create a subdirectory called
.I leaf
-for any non-leaf cgroup which should contain processes, and make sure not to
-create child cgroups of it.
-In the above example, processes which previously would have gone into
+for any nonleaf cgroup which should contain processes, but no child cgroups.
+Thus, processes which previously would have gone into
.I /cg1
would now go into
.IR /cg1/leaf .
-This has the advantage of making explicit the relationship between processes in
+This has the advantage of making explicit
+the relationship between processes in
.I /cg1/leaf
and
.IR /cg1 's