linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-mm@kvack.org, haveblue@us.ibm.com
Subject: Re: One idea to free up page flags on NUMA
Date: Sun, 24 Sep 2006 20:46:37 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0609242041210.19943@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200609250504.58427.ak@suse.de>

On Mon, 25 Sep 2006, Andi Kleen wrote:

> > Right could be in highmem and thus would free up around 20 Megabytes of 
> > low memory.
> But won't the vmemmap need more than the 20MB?

It will need the same as the regular mmap + one / two page table pages 
pointing to the huge pages of the virtual memmap. So if one goes from 
regular mmap to virtual mmap one pays with a few page table pages and the 
need for additional TLBs for lookup. But one can remove the memmap 
entirely from the low memory area.

If we upgrade sparse to be able to use vmemmap then we trade the 
existing sparse structures against the few page table pages plus the 
TLB overhead.

--
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>

  reply	other threads:[~2006-09-25  3:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23  3:02 Christoph Lameter
2006-09-23 16:04 ` Andi Kleen
2006-09-23 16:39   ` Christoph Lameter
2006-09-23 18:43     ` Andi Kleen
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 [this message]
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=Pine.LNX.4.64.0609242041210.19943@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=ak@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox