On Fri, Jun 5, 2009 at 2:55 AM, Balbir Singh<balbir@xxxxxxxxxxxxxxxxxx> wrote: > The point is that there is no single control entity for creating > groups. if run a solution, it might create groups without telling the > user. No one is arbitrating, not even libcgroup. What if someone > changes the cpuset assignment and moves CPUS x to y in an exclusive > cpuset all of a sudden. How do we arbitrate? But in that situation, how do hard limits help? If you can't control when cgroups are being created, and you can't control their shares, how are you going to control their hard limits? Paul -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html