Hello, On Fri, Jul 27, 2012 at 02:15:12PM +0800, Li Zefan wrote: > The cgroup core was extracted from cpuset, so they are deeply tangled. > > There are several issues to resolve with regard to removing cgroup lock from cpuset. > > - there are places that the cgroup hierarchy is travelled. This should be > easy, as cpuset can be made to maintain its hierarchy. Or we can expose limited interface for traversal while protecting hierarchy itself with smaller lock or make the hierarchy safe to traverse with RCU read lock. > - cpuset disallows clearing cpuset.mems/cpuset.cpus if the cgroup is not empty, > which can be guaranteed only by cgroup lock. > > - cpuset disallows a task be attached to a cgroup with empty cpuset.mems/cpuset.cpus, > which again can be guarantted only by cgroup lock. Why can't callbacks enforce the above two? We can keep track of the number of tasks in the cgroup and reject operations as necessary. What's missing? > - cpuset may move tasks from a cgroup to another cgroup (Glauber mentioned this). No idea about this one. Why / how does this happen? Thanks. -- tejun -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>