Re: [RFC][PATCH 1/5] Virtualization/containers: startup

[Kirill Korotaev]

> > So if some people don't like "container", how about just calling it 
> > "context"? The downside of that name is that it's very commonly used 
> > in the kenel, because a lot of things have "contexts". That's why 
> > "container" would be a lot better.
> >
> > I'd suggest
> >
> >     current->container    - the current EFFECTIVE container
> >     current->master_container - the "long term" container.
> >
> > (replace "master" with some other non-S&M term if you want)
>
>
> Hmm.  You actually need a linked list, otherwise you have replaced a one
> level flat structure with a two level one, and you miss out on some of
> the applications.  VServer uses a special structure for this.
Nope! :) This is pointer to current/effective container, which can be 
anywhere in the hierarchy. list should be inside container struct.

Kirill


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/