OpenVZ Forum


Home » Mailing lists » Devel » Re: [PATCH 0/9] namespaces: Introduction
Re: [PATCH 0/9] namespaces: Introduction [message #3278 is a reply to message #3277] Fri, 19 May 2006 16:40 Go to previous messageGo to previous message
Andrew Morton is currently offline  Andrew Morton
Messages: 127
Registered: December 2005
Senior Member
ebiederm@xmission.com (Eric W. Biederman) wrote:
>
> > Herbert Poetzl <herbert@13thfloor.at> wrote:
> >>
> >> let me
> >> give a simple example here:
> >
> > Examples are useful.
> >
> >> "pid virtualization"
> >>
> >> - Linux-VServer doesn't really need that right now.
> >> we are perfectly fine with "pid isolation" here, we
> >> only "virtualize" the init pid to make pstree happy
> >>
> >> - Snapshot/Restart and Migration will require "full"
> >> pid virtualization (that's where Eric and OpenVZ
> >> are heading towards)
> >
> > snapshot/restart/migration worry me. If they require complete
> > serialisation of complex kernel data structures then we have a problem,
> > because it means that any time anyone changes such a structure they need to
> > update (and test) the serialisation.
>
> There is a strict limit to what is user visible, and if it isn't user visible
> we will never need it in a checkpoint. So internal implementation details
> should not matter.

Migration of currently-open sockets (for example) would require storing of
a lot of state, wouldn't it?
 
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
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [PATCH 1/9] namespaces: add nsproxy
Next Topic: [PATCH 0/9] namespaces: Introduction
Goto Forum:
  


Current Time: Wed Jul 23 10:27:47 GMT 2025

Total time taken to generate the page: 0.23301 seconds