On Tue, Aug 10, 2021 at 11:06:03PM -0400, Waiman Long wrote:
For a partition root tree with parent and child partition roots, thisSo, the general rule is that a descendant should never be able to affect or
patch will now prohibit changing parent partition root back to member
as changes to "cpuset.cpus.partition" should not cause those child
partition roots to become invalid.
restrict what an ancestor can do in terms of configuration. This is because
descendant cgroups can be delegated and a system manager sitting at a higher
level in the hierarchy may not have much control over what happens under
Given that we're promoting the error state as the first class citizen in the
interface anyway, wouldn't it be better to keep this in line too?