On Fri, 2005-12-16 at 09:35 -0800, Dave Hansen wrote: > On Thu, 2005-12-15 at 19:28 -0800, Gerrit Huizenga wrote: > > In the pid virtualization, I would think that tasks can move between > > containers as well, > > I don't think tasks can not be permitted to move between containers. As > a simple exercise, imagine that you have two processes with the same > pid, one in container A and one in container B. You wish to have them > both run in container A. They can't both have the same pid. What do > you do? >
Dave, I think you meant "I don't think tasks can <strike>not</strike> be permitted"... Anyway, you make the constraints very clear, unless one can guarantee that the pidspaces don't have any overlaps in vpid usage, there is NOWAY that we can allow this. Otherwise vpids that have been handed to to userspace (think sys_getpid()) need to be revoked (think coherence here). That violates the transparency requirements. > I've been talking a lot lately about how important filesystem isolation > between containers is to implement containers properly. Isolating the > filesystem namespaces makes it much easier to do things like fs-based > shared memory during a checkpoint/resume. If we want to allow tasks to > move around, we'll have to throw out this entire concept. That means > that a _lot_ of things get a notch closer to the too-costly-to-implement > category. > Not only that, as the example of pids already show, while at the surface these might seem as desirable features ( particular since they came up wrt to the CKRM discussion ), there are significant technical limitation to these. -- Hubertus Franke <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
