On 3/7/07, Serge E. Hallyn <serue@xxxxxxxxxx> wrote: > > All that being said, if it were going to save space without overly > complicating things I'm actually not opposed to using nsproxy, but it If space-saving is the main issue, then the latest version of my containers patches uses just a single pointer in the task_struct, and all tasks in the same set of containers (across all hierarchies) will share a single container_group object, which holds the actual pointers to container state. Effectively, container_group is to container as nsproxy is to namespace. Paul _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxx https://lists.osdl.org/mailman/listinfo/containers