From: Rohit Seth <rohitseth@google.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andi Kleen <ak@suse.de>,
CKRM-Tech <ckrm-tech@lists.sourceforge.net>,
devel@openvz.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch02/05]: Containers(V2)- Generic Linux kernel changes
Date: Wed, 20 Sep 2006 17:37:53 -0700 [thread overview]
Message-ID: <1158799073.7207.35.camel@galaxy.corp.google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609201721360.2336@schroedinger.engr.sgi.com>
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.
>
Currently it doesn't track kernel memory. That is why I don't want to
over load any of the existing fields.
> Hmm.... Build a radix tree with pointers to the pages?
>
...my preference is to leave it in page struct...that has non-zero cost.
-rohit
next prev parent reply other threads:[~2006-09-21 0:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 2:18 [patch02/05]: Containers(V2)- Generic Linux kernel changes Rohit Seth
2006-09-20 11:27 ` Andi Kleen
2006-09-20 16:44 ` Rohit Seth
2006-09-20 18:14 ` Andi Kleen
2006-09-20 18:19 ` Rohit Seth
2006-09-20 18:32 ` Andi Kleen
2006-09-21 0:23 ` Christoph Lameter
2006-09-21 0:37 ` Rohit Seth [this message]
2006-09-21 0:41 ` Christoph Lameter
2006-09-21 0:53 ` Rohit Seth
2006-09-21 1:33 ` [ckrm-tech] " Chandra Seetharaman
2006-09-21 22:29 ` Rohit Seth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1158799073.7207.35.camel@galaxy.corp.google.com \
--to=rohitseth@google.com \
--cc=ak@suse.de \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=clameter@sgi.com \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox