Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750792AbWIUAF6 (ORCPT ); Wed, 20 Sep 2006 20:05:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750797AbWIUAF6 (ORCPT ); Wed, 20 Sep 2006 20:05:58 -0400 Received: from omx1-ext.sgi.com ([192.48.179.11]:16843 "EHLO omx1.americas.sgi.com") by vger.kernel.org with ESMTP id S1750792AbWIUAF5 (ORCPT ); Wed, 20 Sep 2006 20:05:57 -0400 Date: Wed, 20 Sep 2006 17:05:44 -0700 From: Paul Jackson To: Christoph Lameter Cc: rohitseth@google.com, ckrm-tech@lists.sourceforge.net, devel@openvz.org, npiggin@suse.de, linux-kernel@vger.kernel.org Subject: Re: [patch00/05]: Containers(V2)- Introduction Message-Id: <20060920170544.b4fd00f4.pj@sgi.com> In-Reply-To: References: <1158718568.29000.44.camel@galaxy.corp.google.com> <1158773208.8574.53.camel@galaxy.corp.google.com> <1158775678.8574.81.camel@galaxy.corp.google.com> <20060920155815.33b03991.pj@sgi.com> <1158795231.7207.21.camel@galaxy.corp.google.com> <1158795569.7207.23.camel@galaxy.corp.google.com> Organization: SGI X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.3; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 828 Lines: 20 > > > Could we equip containers with restrictions on processors and nodes for > > > NUMA? > > Yes. That is something we will have to do (I think part of CPU > > handler-TBD). > > Paul: Will we still need cpusets if that is there? Yes. There's quite a bit more to cpusets than just some form, any form, of CPU and Memory restriction. I can't imagine that Containers, in any form, are going to replicate that API. -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson 1.925.600.0401 - 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/