On Tue, May 29, 2018 at 09:41:29AM -0400, Waiman Long wrote: > + cpuset.sched.domain_root > + A read-write single value file which exists on non-root > + cpuset-enabled cgroups. It is a binary value flag that accepts > + either "0" (off) or "1" (on). This flag is set by the parent > + and is not delegatable. What does "is not delegatable" mean? I think you used to say "is owned by the parent", which is took to mean file ownership is that of the parent directory (..) and not of the current (,), which is slightly odd but works. So if you chown a cgroup to a user, that user will not be able to change the file of it's 'root' (will actually be the root in case of container), but it _can_ change this file for any sub-cgroups it creates, right? So in that respect the feature is delegatable, a container can create sub-partitions. It just cannot change it's 'root' partition, which is consistent with a real root. The only inconsistently left is then that the real root does not have the file at all, vs a container root having it, but not accessible. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
