Messages in this thread | | | Date | Mon, 12 Mar 2007 13:26:32 -0700 | From | Paul Jackson <> | Subject | Re: [ckrm-tech] [PATCH 0/2] resource control file system - aka containers on top of nsproxy! |
| |
vatsa wrote: > This assumes that you can see the global vfs namespace right? > > What if you are inside a container/vserver which restricts your vfs > namespace? i.e /dev/cpusets seen from one container is not same as what > is seen from another container .
Well, yes. But that restriction on the namespace is no doing of cpusets.
It's some vfs namespace restriction, which should be an orthogonal mechanism.
Well, it's probably not orthogonal at present. Cpusets might not yet handle a restricted vfs name space very well.
For example the /proc/<pid>/cpuset path, giving path below /dev/cpuset of task pid's cpuset, might not be restricted. And the set of all CPUs and Memory Nodes that are online, which is visible in various /proc files, and also visible in ones top cpuset, might be inconsistent if restricted vfs namespace mapped you to a different top cpuset.
There are probably other loose ends as well.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.925.600.0401 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |