Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932226AbWITSij (ORCPT ); Wed, 20 Sep 2006 14:38:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932233AbWITSii (ORCPT ); Wed, 20 Sep 2006 14:38:38 -0400 Received: from smtp-out.google.com ([216.239.45.12]:5330 "EHLO smtp-out.google.com") by vger.kernel.org with ESMTP id S932226AbWITSih (ORCPT ); Wed, 20 Sep 2006 14:38:37 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:subject:from:reply-to:to:cc:in-reply-to:references: content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=rPwvFkiPkkXhqpoMyiZivz2oe9ZL+JgJecbSjVvvKwKOJXlsUNCvuTp3yjzt7RRaI 6lN+T6mLqNloyqvIUoYmA== Subject: Re: [patch00/05]: Containers(V2)- Introduction From: Rohit Seth Reply-To: rohitseth@google.com To: Peter Zijlstra Cc: Christoph Lameter , Nick Piggin , CKRM-Tech , devel@openvz.org, linux-kernel , Linux Memory Management In-Reply-To: <1158776824.28174.29.camel@lappy> References: <1158718568.29000.44.camel@galaxy.corp.google.com> <4510D3F4.1040009@yahoo.com.au> <1158751720.8970.67.camel@twins> <4511626B.9000106@yahoo.com.au> <1158767787.3278.103.camel@taijtu> <451173B5.1000805@yahoo.com.au> <1158774657.8574.65.camel@galaxy.corp.google.com> <1158775586.28174.27.camel@lappy> <1158776099.8574.89.camel@galaxy.corp.google.com> <1158776824.28174.29.camel@lappy> Content-Type: text/plain Organization: Google Inc Date: Wed, 20 Sep 2006 11:38:08 -0700 Message-Id: <1158777488.8574.103.camel@galaxy.corp.google.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 703 Lines: 20 On Wed, 2006-09-20 at 20:27 +0200, Peter Zijlstra wrote: > Yes, I read that in your patches, I was wondering how the cpuset > approach would handle this. > > Neither are really satisfactory for shared mappings. > In which way? We could have the per container flag indicating whether to charge this container for shared mapping that it initiates or to the container where mapping belongs...or is there something different that you are referring. -rohit - 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/