From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: mem_map
Date: Mon, 09 May 2005 13:31:45 +0000 [thread overview]
Message-ID: <17023.26177.377922.550436@napali.hpl.hp.com> (raw)
In-Reply-To: <851caabb05050607291364149a@mail.gmail.com>
>>>>> On Fri, 6 May 2005 19:59:59 +0530, Vaibhav Sharma <vaibhav.sh@gmail.com> said:
Vaibhav> hi all, Can any body provide any information for the
Vaibhav> significance of "CONFIG_VIRTUAL_MEM_MAP"?
Turning on this option puts the Linux physical memory-map (mem_map)
into virtual memory rather than physical memory. Doing so can be an
advantage on machines which have holes in the physical memory. For
example, on zx1-based machines, physical memory 1GB-4GB shows up at an
address above 257GB so there is a hole of about 256GB below that
address.
There are other ways to manage (huge) holes in physical memory space,
but with the large page-sizes (64MB or 16MB) we use on ia64 for
identity-mapping kernel space, this approach seems to work quite well.
--david
prev parent reply other threads:[~2005-05-09 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 14:41 mem_map Vaibhav Sharma
2005-05-06 15:56 ` mem_map Grant Grundler
2005-05-09 13:31 ` David Mosberger [this message]
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=17023.26177.377922.550436@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.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