From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, haveblue@us.ibm.com
Subject: Re: One idea to free up page flags on NUMA
Date: Sat, 23 Sep 2006 20:43:10 +0200 [thread overview]
Message-ID: <200609232043.10434.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0609230937140.15303@schroedinger.engr.sgi.com>
On Saturday 23 September 2006 18:39, Christoph Lameter wrote:
> On Sat, 23 Sep 2006, Andi Kleen wrote:
>
> > And what would we use them for?
>
> Maybe a container number?
>
> Anyways the scheme also would reduce the number of lookups needed and
> thus the general footprint of the VM using sparse.
So far most users (distributions) are not using sparse yet anyways.
> I just looked at the arch code for i386 and x86_64 and it seems that both
> already have page tables for all of memory.
i386 doesn't map all of memory.
> It seems that a virtual memmap
> like this would just eliminate sparse overhead and not add any additional
> page table overhead.
You would have new mappings with new overhead, no?
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-09-23 18:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 3:02 One idea to free up page flags on NUMA Christoph Lameter
2006-09-23 16:04 ` Andi Kleen
2006-09-23 16:39 ` Christoph Lameter
2006-09-23 18:43 ` Andi Kleen [this message]
2006-09-24 1:57 ` Christoph Lameter
2006-09-24 7:24 ` Andi Kleen
2006-09-25 0:31 ` Christoph Lameter
2006-09-25 3:04 ` Andi Kleen
2006-09-25 3:46 ` Christoph Lameter
2006-09-23 19:24 ` Dave Hansen
2006-09-24 1:56 ` Christoph Lameter
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=200609232043.10434.ak@suse.de \
--to=ak@suse.de \
--cc=clameter@sgi.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.