Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932076AbWIUWaM (ORCPT ); Thu, 21 Sep 2006 18:30:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932075AbWIUWaM (ORCPT ); Thu, 21 Sep 2006 18:30:12 -0400 Received: from smtp-out.google.com ([216.239.45.12]:6715 "EHLO smtp-out.google.com") by vger.kernel.org with ESMTP id S932066AbWIUWaK (ORCPT ); Thu, 21 Sep 2006 18:30:10 -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=MSeuk5BbyeoIsCuLNdc+95CfmSzHL9QIoQAUmeN5/KjyIMsXwLZ3wj4G4tbRvWN7q L9nG6wtqiCDA8vkn2dSFw== Subject: Re: [ckrm-tech] [patch02/05]: Containers(V2)- Generic Linux kernel changes From: Rohit Seth Reply-To: rohitseth@google.com To: sekharan@us.ibm.com Cc: Christoph Lameter , Andi Kleen , linux-kernel , devel@openvz.org, CKRM-Tech In-Reply-To: <1158802412.6536.127.camel@linuxchandra> References: <1158718722.29000.50.camel@galaxy.corp.google.com> <1158770670.8574.26.camel@galaxy.corp.google.com> <200609202014.48815.ak@suse.de> <1158802412.6536.127.camel@linuxchandra> Content-Type: text/plain Organization: Google Inc Date: Thu, 21 Sep 2006 15:29:45 -0700 Message-Id: <1158877786.7207.74.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: 1712 Lines: 41 On Wed, 2006-09-20 at 18:33 -0700, Chandra Seetharaman wrote: > On Wed, 2006-09-20 at 17:23 -0700, Christoph Lameter wrote: > > On Wed, 20 Sep 2006, Andi Kleen wrote: > > > > > There are lots of different cases. At least for anonymous memory > > > ->mapping should be free. Perhaps that could be used for anonymous > > > memory and a separate data structure for the important others. > > > > mapping is used for swap and to point to the anon vma. > > > > > slab should have at least one field free too, although it might be a different > > > one (iirc Christoph's rewrite uses more than the current slab, but it would > > > surprise me if he needed all) > > > > slab currently has lots of fields free but my rewrite uses all of them. > > And AFAICT this patchset does not track slab pages. > > > > Hmm.... Build a radix tree with pointers to the pages? > > Yes, that would be a way to isolate the overhead. > As said earlier, the additional cost is not really that much. And if we do get additional benefit of proper cache alignment for page struct because of this additional pointer then it could be a almost zero cost. And in mm kernel, I also see PAGE_OWNER defined which puts the whole page struct out of sync with caches. Christoph, Please let me know if there is still a placeholder for container pointer ONLY for kernel pages. I think it is easy to do away with per page pointer for user land as it can be stored in anon_vma or mappings. -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/