Hello, On Tue, May 10, 2022 at 11:34:12AM -0400, Waiman Long wrote: > + External events like hotplug or changes to "cpuset.cpus" can > + cause a valid partition root to become invalid and vice versa. > + Note that a task cannot be moved to a cgroup with empty > + "cpuset.cpus.effective". > + > + For a valid partition root or an invalid partition root with > + the exclusivity rule enabled, changes made to "cpuset.cpus" > + that violate the exclusivity rule will not be allowed. My memory is failing but this is the same thing that we were discussing before, right? The point was that the different behaviors re. system events and config actions seemed unncessary and IIRC Michal was of the same opinion (please correct me if I'm misremembering). > + A valid non-root parent partition may distribute out all its CPUs > + to its child partitions when there is no task associated with it. I'm probably forgetting something. Was this necessary because of threaded cgroup support because otherwise the above condition is superflous? Thanks. -- tejun
