public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH 4/4] vmm: Use a static memory map
Date: Thu, 12 Oct 2006 21:40:25 +0000	[thread overview]
Message-ID: <000001c6ee47$0764e7e0$db34030a@amr.corp.intel.com> (raw)
In-Reply-To: <20061012191828.21498.95831.sendpatchset@schroedinger.engr.sgi.com>

Christoph Lameter wrote on Thursday, October 12, 2006 12:18 PM
> IA64 currently uses a dynamically configured memory map that is taken off
> the end of VMALLOC space. This means that we do some tweaking with some
> core constants that now refer to variables and we keep having to
> get the address of the virtual memory map and the limits from memory.
> This patch makes pfn_to_page and page_to_pfn possible without referencing
> any memory location.
> 
> So, the size of the virtual memory map is always less than 8 Terabyte.
> 
> I think its reasonable to take these 8 Terabyte away from the 128 Terabyte
> that we currently reserve for support for VMALLOC space.
> 
> Advantages:
> - virt_to_page, page_address, pfn_to_page, page_to_pfn become simple address
>   calculations without a memory reference.

I like the concept a lot.


> - This patch will enable later patches to move the virtual memory map into
>   another region with a larger page size. Larger page sizes will reduce
>   TLB pressure.

I like that even more, which region are you going to move it to?

  reply	other threads:[~2006-10-12 21:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 19:18 [PATCH 4/4] vmm: Use a static memory map Christoph Lameter
2006-10-12 21:40 ` Chen, Kenneth W [this message]
2006-10-12 22:18 ` Luck, Tony
2006-10-13  0:26 ` Christoph Lameter
2006-10-13  0:29 ` Christoph Lameter
2006-10-13  0:56 ` KAMEZAWA Hiroyuki
2006-10-13  1:13 ` 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='000001c6ee47$0764e7e0$db34030a@amr.corp.intel.com' \
    --to=kenneth.w.chen@intel.com \
    --cc=linux-ia64@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