Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750935AbWBCQe4 (ORCPT ); Fri, 3 Feb 2006 11:34:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751205AbWBCQe4 (ORCPT ); Fri, 3 Feb 2006 11:34:56 -0500 Received: from mailhub.sw.ru ([195.214.233.200]:59228 "EHLO relay.sw.ru") by vger.kernel.org with ESMTP id S1750935AbWBCQe4 (ORCPT ); Fri, 3 Feb 2006 11:34:56 -0500 Message-ID: <43E38643.30501@sw.ru> Date: Fri, 03 Feb 2006 19:35:15 +0300 From: Kirill Korotaev User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.2.1) Gecko/20030426 X-Accept-Language: ru-ru, en MIME-Version: 1.0 To: Dave Hansen CC: "Eric W. Biederman" , Linus Torvalds , Hubertus Franke , Greg KH , Alan Cox , "Serge E. Hallyn" , Arjan van de Ven , Linux Kernel Mailing List , Cedric Le Goater Subject: Re: RFC [patch 13/34] PID Virtualization Define new task_pid api 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> <43E21BD0.6000606@sw.ru> <43E2249D.8060608@sw.ru> <43E22DCA.3070004@sw.ru> <43E335D4.9000401@sw.ru> <1138981528.6189.16.camel@localhost.localdomain> In-Reply-To: <1138981528.6189.16.camel@localhost.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1133 Lines: 25 >>How can you migrate application which consists of two processes doing >>IPC via signals? They are not tired inside kernel anyhow and there is >>no way to automatically detect that both should be migrated together. >>VPSs what provides you such kind of boundaries of what should be >>considered as a whole. > > > Could you explain a little bit _how_ VPSs provide this? OpenVZ virtualizes kernel resources such as IPC making them per-VPS. Processes in VPS deal with such virtualized resources, so they efficiently should be migrated together. That's it - a whole container with its resources should be considered as a whole. Signals are not virtualized in this manner since they are rather per-task resource, but OpenVZ introduces strict boundaries in kernel which make sure that no any 3rd task from another container (VPS) will be participating in the communication. Kirill - 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/