On Fri, 2009-03-20 at 16:48 -0400, Oren Laadan wrote: > Does that scale well with many (1000's) of tasks ? > > (The motivation to expose 'nsproxy_objref' to user space was to allow > user-space to decide on a sequence of clones/unshared that will create > an equivalent process tree with space-efficient nsproxy's). OK, so you're saying that there's no way for userspace to tell that a set of tasks share an nsproxy other than exporting that nsproxy? > Perhaps instead of nsproxy_equal() we could use an 'nsproxy_objref' > to know a-priori that it is common, and save the "compare-and-swap" > phase altogether. Sure, that's workable. The important thing is that it is an optimization that can be left for later. -- Dave _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
