Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030395AbWBHBQX (ORCPT ); Tue, 7 Feb 2006 20:16:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030397AbWBHBQX (ORCPT ); Tue, 7 Feb 2006 20:16:23 -0500 Received: from watts.utsl.gen.nz ([202.78.240.73]:4510 "EHLO mail.utsl.gen.nz") by vger.kernel.org with ESMTP id S1030395AbWBHBQW (ORCPT ); Tue, 7 Feb 2006 20:16:22 -0500 Message-ID: <43E94651.2090009@vilain.net> Date: Wed, 08 Feb 2006 14:16:01 +1300 From: Sam Vilain User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Fox Cc: Hubertus Franke , Rik van Riel , "Eric W. Biederman" , Kirill Korotaev , Linus Torvalds , Andrew Morton , linux-kernel@vger.kernel.org, clg@fr.ibm.com, haveblue@us.ibm.com, greg@kroah.com, alan@lxorguk.ukuu.org.uk, serue@us.ibm.com, arjan@infradead.org, kuznet@ms2.inr.ac.ru, saw@sawoct.com, devel@openvz.org, Dmitry Mishin , Andi Kleen Subject: Re: [PATCH 1/4] Virtualization/containers: introduction References: <43E7C65F.3050609@openvz.org> <43E83E8A.1040704@vilain.net> <43E8D160.4040803@watson.ibm.com> <43E92602.8040403@vilain.net> <1139364483.7169.20.camel@localhost.localdomain> In-Reply-To: <1139364483.7169.20.camel@localhost.localdomain> X-Enigmail-Version: 0.92.1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1267 Lines: 26 Kevin Fox wrote: >>>The container is just an umbrella object that ties every "virtualized" >>>subsystem together. >>I like this description; it matches roughly with the concepts as >>presented by vserver; there is the process virtualisation (vx_info), and >>the network virtualisation (nx_info) of Eric's that has been integrated >>to the vserver 2.1.x development branch. However the vx_info has become >>the de facto umbrella object space as well. These could almost >>certainly be split out without too much pain or incurring major >>rethinks. > How does all of this tie in with CPU Sets? It seems to me, they have > something not unlike a container already that supports nesting. Yes, I saw that. AIUI that's mainly about binding groups of processes to CPUs, to defeat Amdahl's law when it rears its head. It fits into the containers model as a hard partitioning feature, but is a lot more crude than the CPU Token Bucket scheduler in Linux-VServer. No doubt both CPU allocation strategies will be useful. Sam. - 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/