All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 25 Sep 2006 05:04:58 +0200	[thread overview]
Message-ID: <200609250504.58427.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0609241730470.19511@schroedinger.engr.sgi.com>

On Monday 25 September 2006 02:31, Christoph Lameter wrote:
> On Sun, 24 Sep 2006, Andi Kleen wrote:
> 
> > > Hmmm... It only maps the kernel text segment?
> > Only lowmem (normally upto ~900MB)
> > 
> > But virtual memory is very scarce so I don't know where a new map for mem_map
> > would come from. Ok you could try to move the physical location of mem_map to 
> > somewhere not in lowmem I suppose.
> 
> 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?

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

  reply	other threads:[~2006-09-25  3:04 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
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 [this message]
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=200609250504.58427.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.