Hello, On Tue, May 01, 2018 at 04:33:45PM -0400, Waiman Long wrote: > I think that will work too. We currently don't have a flag to make a > file visible on first-level children only, but it shouldn't be hard to > make one. I think it'd be fine to make the flag file exist on all !root cgroups but only writable on the first level children. > Putting CPUs into an isolated child cpuset means removing it from the > root's effective CPUs. So I would probably like to expose the read-only > cpus.effective in the root cgroup so that we can check changes in the > effective cpu list. Ah, yeah, that makes sense. > I will renew the patchset will your suggestion. Thank you very much. -- tejun -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
