Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751748AbWITQ0z (ORCPT ); Wed, 20 Sep 2006 12:26:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751751AbWITQ0z (ORCPT ); Wed, 20 Sep 2006 12:26:55 -0400 Received: from omx2-ext.sgi.com ([192.48.171.19]:25042 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S1751748AbWITQ0z (ORCPT ); Wed, 20 Sep 2006 12:26:55 -0400 Date: Wed, 20 Sep 2006 09:26:41 -0700 (PDT) From: Christoph Lameter To: Nick Piggin cc: rohitseth@google.com, CKRM-Tech , devel@openvz.org, linux-kernel , Linux Memory Management Subject: Re: [patch00/05]: Containers(V2)- Introduction In-Reply-To: <4510D3F4.1040009@yahoo.com.au> Message-ID: References: <1158718568.29000.44.camel@galaxy.corp.google.com> <4510D3F4.1040009@yahoo.com.au> 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: 632 Lines: 14 On Wed, 20 Sep 2006, Nick Piggin wrote: > I'm not sure about containers & workload management people, but from > a core mm/ perspective I see no reason why this couldn't get in, > given review and testing. Great! Nack. We already have the ability to manage workloads. We may want to extend the existing functionality but this is duplicating what is already available through cpusets. - 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/