Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750709AbWITXbc (ORCPT ); Wed, 20 Sep 2006 19:31:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750716AbWITXbc (ORCPT ); Wed, 20 Sep 2006 19:31:32 -0400 Received: from omx2-ext.sgi.com ([192.48.171.19]:11156 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S1750709AbWITXbb (ORCPT ); Wed, 20 Sep 2006 19:31:31 -0400 Date: Wed, 20 Sep 2006 16:31:22 -0700 (PDT) From: Christoph Lameter To: lhms-devel@lists.sourceforge.net cc: Rohit Seth , Paul Jackson , ckrm-tech@lists.sourceforge.net, devel@openvz.org, npiggin@suse.de, linux-kernel@vger.kernel.org Subject: Re: [patch00/05]: Containers(V2)- Introduction In-Reply-To: <1158794808.7207.14.camel@galaxy.corp.google.com> Message-ID: 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> <1158794808.7207.14.camel@galaxy.corp.google.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 652 Lines: 14 On Wed, 20 Sep 2006, Rohit Seth wrote: > Absolutely. Since these containers are not (hard) partitioning the > memory in any way so it is easy to change the limits (effectively > reducing and increasing the memory limits for tasks belonging to > containers). As you said, memory hot-un-plug is important and it is > non-trivial amount of work. Maybe the hotplug guys want to contribute to the discussion? - 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/