On Tue, Apr 03, 2007 at 10:49:49AM -0700, Paul Menage wrote: > > 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]. > > I was thinking of queries from userspace.
User space queries like "what is the cpuset to which this task belongs", where the answer needs to be something of the form "/dev/cpuset/C1"? The patches address that requirement atm by having a dentry pointer in struct cpuset itself. Do you see similar queries coming in for every resource controller object (show me the path of cpu_acct, cpu_ctl, rss_ctl ... objects to which this task belongs)? IMO that will not be the case, in which case we can avoid adding N pointers (N = max hierarchies) in nsproxy just to support queries of those sort. If additional resource objects need to support such queries in future, we could add a dentry pointer in those objects as and when the need arises. -- Regards, vatsa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
