Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964824AbWBGJqh (ORCPT ); Tue, 7 Feb 2006 04:46:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964825AbWBGJqh (ORCPT ); Tue, 7 Feb 2006 04:46:37 -0500 Received: from mtagate2.uk.ibm.com ([195.212.29.135]:18170 "EHLO mtagate2.uk.ibm.com") by vger.kernel.org with ESMTP id S964824AbWBGJqg (ORCPT ); Tue, 7 Feb 2006 04:46:36 -0500 Message-ID: <43E86C73.2070608@fr.ibm.com> Date: Tue, 07 Feb 2006 10:46:27 +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: Alexey Kuznetsov CC: "Serge E. Hallyn" , Dave Hansen , Kirill Korotaev , arjan@infradead.org, frankeh@watson.ibm.com, mrmacman_g4@mac.com, alan@lxorguk.ukuu.org.uk, Linux Kernel Mailing List , devel@openvz.org Subject: Re: [RFC][PATCH 5/7] VPIDs: vpid/pid conversion in VPID enabled case References: <43E22B2D.1040607@openvz.org> <43E23398.7090608@openvz.org> <1138899951.29030.30.camel@localhost.localdomain> <20060203105202.GA21819@ms2.inr.ac.ru> <43E35105.3080208@fr.ibm.com> <20060203140229.GA16266@ms2.inr.ac.ru> <43E38D40.3030003@fr.ibm.com> <20060206094843.GA6013@ms2.inr.ac.ru> <20060206145104.GB11887@sergelap.austin.ibm.com> <20060206155101.GA22522@ms2.inr.ac.ru> In-Reply-To: <20060206155101.GA22522@ms2.inr.ac.ru> 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: 1384 Lines: 28 Alexey Kuznetsov wrote: > The question was not about openvz, it was about (container,pid) approach. > How are you going to reap chidren without a child reaper inside container? > If you reparent all the children to a single init in root container, > what does wait() return? In openvz it returns global pid and child is buried > in peace. If you do not have global pid, you cannot just return private pid. I think the "child reaper" question is not related to the (container,pid) approach or the vpid approach. This is another question on who is the parent of a container and how does it behaves. We have choosen to first follow a simple "path", complete pid isolation being the main constraint : a container is created by exec'ing a process in it. That first process is detached from its parent processes and becomes child of init (already running), session leader, and process group leader. We could eventually add a daemon to act as a init process for the container. Now, there are other ways of seeing a container parenthood, openvz, eric, vserver, etc. We should agree on this or find a way to have different model cohabitate. 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/