Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750927AbWIUWA2 (ORCPT ); Thu, 21 Sep 2006 18:00:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751630AbWIUWA2 (ORCPT ); Thu, 21 Sep 2006 18:00:28 -0400 Received: from omx1-ext.sgi.com ([192.48.179.11]:17896 "EHLO omx1.americas.sgi.com") by vger.kernel.org with ESMTP id S1750924AbWIUWA1 (ORCPT ); Thu, 21 Sep 2006 18:00:27 -0400 Date: Thu, 21 Sep 2006 14:59:46 -0700 From: Paul Jackson To: "Paul Menage" Cc: sekharan@us.ibm.com, npiggin@suse.de, ckrm-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org, rohitseth@google.com, devel@openvz.org, clameter@sgi.com Subject: Re: [ckrm-tech] [patch00/05]: Containers(V2)- Introduction Message-Id: <20060921145946.8d9ace73.pj@sgi.com> In-Reply-To: <6599ad830609211310s4e036e55h89bab26432d83c11@mail.google.com> References: <1158718568.29000.44.camel@galaxy.corp.google.com> <1158777240.6536.89.camel@linuxchandra> <1158798715.6536.115.camel@linuxchandra> <20060920173638.370e774a.pj@sgi.com> <6599ad830609201742h71d112f4tae8fe390cb874c0b@mail.google.com> <1158803120.6536.139.camel@linuxchandra> <6599ad830609201852k12cee6eey9086247c9bdec8b@mail.google.com> <1158869186.6536.205.camel@linuxchandra> <6599ad830609211310s4e036e55h89bab26432d83c11@mail.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: 755 Lines: 18 Paul wrote: > But, there's no reason that the OpenVZ resource control mechanisms > couldn't be hooked into a generic process container mechanism along > with cpusets and RG. Can the generic container avoid performance bottlenecks due to locks or other hot cache lines on the main code paths for fork, exit, page allocation and task scheduling? -- 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/