Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932195AbWBPRyY (ORCPT ); Thu, 16 Feb 2006 12:54:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932337AbWBPRyY (ORCPT ); Thu, 16 Feb 2006 12:54:24 -0500 Received: from e4.ny.us.ibm.com ([32.97.182.144]:33446 "EHLO e4.ny.us.ibm.com") by vger.kernel.org with ESMTP id S932195AbWBPRyX (ORCPT ); Thu, 16 Feb 2006 12:54:23 -0500 Date: Thu, 16 Feb 2006 11:53:26 -0600 From: "Serge E. Hallyn" To: "Eric W. Biederman" Cc: "Serge E. Hallyn" , Kirill Korotaev , linux-kernel@vger.kernel.org, vserver@list.linux-vserver.org, Herbert Poetzl , Alan Cox , Dave Hansen , Arjan van de Ven , Suleiman Souhlal , Hubertus Franke , Cedric Le Goater , Kyle Moffett , Greg , Linus Torvalds , Andrew Morton , Greg KH , Rik van Riel , Alexey Kuznetsov , Andrey Savochkin , Kirill Korotaev , Andi Kleen , Benjamin Herrenschmidt , Jeff Garzik , Trond Myklebust , Jes Sorensen Subject: Re: (pspace,pid) vs true pid virtualization Message-ID: <20060216175326.GA11974@sergelap.austin.ibm.com> References: <20060215145942.GA9274@sergelap.austin.ibm.com> <20060216142928.GA22358@sergelap.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1382 Lines: 44 Quoting Eric W. Biederman (ebiederm@xmission.com): > > I think it should be acceptable if a pidspace is visible in all it's > > ancestor pidspaces. I.e. if I create pspace2 and pspace3 from pid 234 > > in pspace1, then pspace2 doesn't need to be able to address pspace3 > > and vice versa. > > A good rule. Now consider pspace 4 which is a child of pid 567 > in pspace 3. > > What should pspace 3 see? Implementation dependent. What I'd like to see is: > What should pspace 3 see? The pid of the init process for pspace 4. > What should pspace 1 see? The pid of the init process for pspace 3. > What happens when you migrate pspace 3 into a different pspace > on a different machine? Nothing special. "Migrate" was just a checkpoint (from pspace 1) and a resume (from pspace N on some machine). So now pspace N on the new machine has created a new pspace - which happens to be immediately populated with the contents of the old pspace 3 - and see the pid of the init process of this new pspace. > Is there a sane implementation for this? IMO, definately yes. But I haven't tried it, so my opinion is just that. -serge - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/