On Tue, Apr 03, 2007 at 10:30:28AM -0700, Paul Menage wrote: > So how do you implement something like the /proc/<PID>/container info > file in my patches? I havent implemented that yet, so I will look at your next question: > (Or more generally, tell which container a task is > in for a given hierarchy?) Why is the hierarchy bit important here? Usually controllers need to know "tell me what cpuset this task belongs to", which is answered by tsk->nsproxy->ctlr_data[CPUSET_ID]. The only usecase of storing hierarchy I have found is in container_clone() where you need to create a directory in the right hierarchy, so knowing the hierarchy to which a controller is bound becomes important. -- Regards, vatsa _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
