Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750711AbWAXVLG (ORCPT ); Tue, 24 Jan 2006 16:11:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750716AbWAXVLG (ORCPT ); Tue, 24 Jan 2006 16:11:06 -0500 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:24527 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1750711AbWAXVLF (ORCPT ); Tue, 24 Jan 2006 16:11:05 -0500 Subject: Re: RFC [patch 13/34] PID Virtualization Define new task_pid api From: Alan Cox To: "Eric W. Biederman" Cc: Hubertus Franke , Dave Hansen , Greg KH , "Serge E. Hallyn" , Arjan van de Ven , linux-kernel@vger.kernel.org, Cedric Le Goater In-Reply-To: References: <20060117143258.150807000@sergelap> <20060117143326.283450000@sergelap> <1137511972.3005.33.camel@laptopd505.fenrus.org> <20060117155600.GF20632@sergelap.austin.ibm.com> <1137513818.14135.23.camel@localhost.localdomain> <1137518714.5526.8.camel@localhost.localdomain> <20060118045518.GB7292@kroah.com> <1137601395.7850.9.camel@localhost.localdomain> <43D14578.6060801@watson.ibm.com> <43D52592.8080709@watson.ibm.com> <1138050684.24808.29.camel@localhost.localdomain> <1138062125.24808.47.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 24 Jan 2006 21:11:00 +0000 Message-Id: <1138137060.14675.73.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1338 Lines: 31 On Maw, 2006-01-24 at 12:26 -0700, Eric W. Biederman wrote: > There is at least NFS lockd that appreciates having a single integer > per process unique identifier. So there is a practical basis for > wanting such a thing. Which gets us back to refcounting. > At least for this first round I think talking about a kpid > as a container, pid pair makes a lot of sense for the moment, as > the other implementations just confuse things. As an abstract object a kpid to me means a single identifier which uniquely identifies the process and which in its component parts be they pointers or not uniquely identifies the process in the container and the container in the system, both correctly refcounted against re-use. > However it looks to me that the biggest challenge right now about > development is the size of a patch to change any one of these things. Thats where we disagree strongly. Wrappers hide, confuse and obscure. We want the workings brutally and clearly visible so that people don't make assumptions and have nasty accidents. Its like typdedefs and overuse of defines. Alan - 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/