From: Andi Kleen <ak@suse.de>
To: rohitseth@google.com
Cc: 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 20:32:59 +0200 [thread overview]
Message-ID: <200609202032.59329.ak@suse.de> (raw)
In-Reply-To: <1158776378.8574.95.camel@galaxy.corp.google.com>
> It is not free for anonymous memory as it is overloaded with pointer to
> anon_vma.
Sorry. But ->index should be free there.
> I think one single pointer consistent across all page usages
> is just so much cleaner and simple...
It just costs you 0.2% of all your memory in all cases. Too much imho.
-Andi
next prev parent reply other threads:[~2006-09-20 18:33 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 [this message]
2006-09-21 0:23 ` Christoph Lameter
2006-09-21 0:37 ` Rohit Seth
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=200609202032.59329.ak@suse.de \
--to=ak@suse.de \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rohitseth@google.com \
/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