On Thu, Oct 09, 2014 at 01:50:52PM +0530, Preeti U Murthy wrote: > However what remains to be answered is that the V2 of cgroup design - > the default hierarchy, tracks hotplug operations for children cgroups as > well. Tejun, Li, will not the concerns that Peter raised above hold for > the default hierarchy as well? I don't think the legacy one is a good design. Kernel shouldn't lose configurations in an irreversible way and the legacy one is also making random cpuset flips by migrating tasks upwards anyway. In terms of hotunplug behavior, the legacy and unified ones behave the same. The only difference is that the configuration is independent of the current state and the configured behavior is restored when the cpus come back. The other side is that the legacy hierarchy behavior simply can't be allowed when the hierarchy is shared among multiple controllers as in the unified hierarchy. It affects all other controllers attached to the hierarchy. That said, we can't change the behavior on the legacy one. It's a very userland visible behavior. We simply can't change it, so unfortunately you're stuck with it at least on the legacy hierarchy. Thanks. -- 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
