Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751299AbWCAWGq (ORCPT ); Wed, 1 Mar 2006 17:06:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751301AbWCAWGq (ORCPT ); Wed, 1 Mar 2006 17:06:46 -0500 Received: from mtagate1.de.ibm.com ([195.212.29.150]:45620 "EHLO mtagate1.de.ibm.com") by vger.kernel.org with ESMTP id S1751299AbWCAWGp (ORCPT ); Wed, 1 Mar 2006 17:06:45 -0500 Message-ID: <44061AEA.5040304@fr.ibm.com> Date: Wed, 01 Mar 2006 23:06:34 +0100 From: Cedric Le Goater User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Herbert Poetzl CC: Kirill Korotaev , "Eric W. Biederman" , linux-kernel@vger.kernel.org, vserver@list.linux-vserver.org, "Serge E. Hallyn" , Alan Cox , Dave Hansen , Arjan van de Ven , Suleiman Souhlal , Hubertus Franke , 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: [RFC][PATCH 04/20] pspace: Allow multiple instaces of the process id namespace References: <43ECF803.8080404@sw.ru> <43F04FD6.5090603@sw.ru> <43F31972.3030902@sw.ru> <20060215133131.GD28677@MAIL.13thfloor.at> <43F9A80A.6050808@sw.ru> <20060220123427.GA17478@MAIL.13thfloor.at> <43F9CE1C.2020603@sw.ru> <20060220150811.GA18841@MAIL.13thfloor.at> In-Reply-To: <20060220150811.GA18841@MAIL.13thfloor.at> X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1000 Lines: 28 Herbert Poetzl wrote: >>>>First of all, I don't think syscalls like >>>>"do_something and exec" should be introduced. >>> >>>Linux-VServer does not have any of those syscalls >>>and it works quite well, so why should we need such >>>syscalls? >> >>My question is the same! Why? > > > because we don't need them?! I think that the reason behind such syscalls is to make sure that the process is "clean" when it enters a new container. "clean" means that the process is not holding in memory an identifier, like a pid for instance, that doesn't make sense in the new container. This is really a edge case which supposes that processes changing containers don't know what they are doing. This case also depends on how identifiers will be virtualized. C. - 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/