OpenVZ Forum


Home » Mailing lists » Devel » semantics for namespace naming
Re: semantics for namespace naming [message #17040 is a reply to message #17021] Wed, 13 December 2006 21:47 Go to previous messageGo to previous message
Herbert Poetzl is currently offline  Herbert Poetzl
Messages: 239
Registered: February 2006
Senior Member
On Wed, Dec 13, 2006 at 10:36:33AM -0800, Dave Hansen wrote:
> On Wed, 2006-12-13 at 08:35 -0600, Serge E. Hallyn wrote:
> > 
> >         struct container {
> >                 struct container *parent;
> >                 char *name;
> >                 struct nsproxy *nsproxy;
> >                 struct list_head children;
> >         };
> >         struct nsproxy {
> >                 ...
> >                 struct container *container;
> >         };
> 
> Why does a container need a pointer to an nsproxy?  I think I missed
> that.  Is that the "default" set of namespaces for tasks in that
> container?

IMHO it is mainly required to _enter_ the container
in some controlled way (at least that is what we
use the nsproxy reference for)

best,
Herbert

> -- Dave
> 
> _______________________________________________
> Containers mailing list
> Containers@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/containers
_______________________________________________
Containers mailing list
Containers@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/containers
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [PATCH] compat offsets size change
Next Topic: [PATCH 1/12] L2 network namespace: current network namespace operations
Goto Forum:
  


Current Time: Sun Sep 01 14:23:17 GMT 2024

Total time taken to generate the page: 0.05821 seconds