From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Arne Georg Gleditsch <arne.gleditsch@dolphinics.no>
Cc: Andi Kleen <andi@firstfloor.org>,
Zhao Forrest <forrest.zhao@gmail.com>,
discuss@x86-64.org, linux-kernel@vger.kernel.org,
yhlu.kernel@gmail.com, mingo@elte.hu, ak@suse.de
Subject: Re: Does Linux have plan to support memory hole remapping?
Date: Wed, 9 Apr 2008 09:34:14 -0400 [thread overview]
Message-ID: <20080409133414.GA2160@csclub.uwaterloo.ca> (raw)
In-Reply-To: <kjmr6dfxsqf.fsf@pelargir.dolphinics.no>
On Wed, Apr 09, 2008 at 11:50:00AM +0200, Arne Georg Gleditsch wrote:
> Hm, wouldn't the given e820 map and mtrr listing indicate that 512M were
> actually remapped to 32G+ in this case?
The mtrr does list the 512MB as being remapped. It sais there was 32GB
starting at 0, and 512MB starting at 32GB, and then that there was an
uncacheable 512MB hole at 3.5GB. So the mtrr does say everything looks
right.
The e820 map also shows it:
BIOS-e820: 0000000000000000 - 0000000000098c00 (usable)
625,664 bytes
BIOS-e820: 0000000000100000 - 00000000dffa0000 (usable)
3,756,654,592 bytes
BIOS-e820: 0000000100000000 - 0000000820000000 (usable)
30,601,641,984 bytes
Total of 34,358,922,240 bytes or 32767.221 MiB. Seems rather close to
the full 32768 MiB in the system. So looks to me like the mtrr and e820
covers all the ram. Maybe the kernel looses some of it somewhere for
other purposes.
Isn't there usually a line in dmesg similar to this:
Memory: 1023120k/1048256k available (1927k kernel code, 24748k reserved, 868k data, 176k init)
Maybe it can show how much the kernel reserved for itself in this case.
--
Len Sorensen
prev parent reply other threads:[~2008-04-09 13:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 7:54 Zhao Forrest
2008-04-09 8:01 ` Andi Kleen
2008-04-09 8:37 ` Matti Aarnio
2008-04-09 8:49 ` Andi Kleen
2008-04-09 8:54 ` Ingo Molnar
2008-04-09 9:03 ` Andi Kleen
2008-04-10 0:34 ` Kasper Sandberg
2008-04-10 2:09 ` H. Peter Anvin
2008-04-10 12:41 ` Kasper Sandberg
2008-04-10 6:51 ` Andi Kleen
2008-04-09 9:04 ` Zhao Forrest
2008-04-09 9:13 ` Andi Kleen
2008-04-10 6:51 ` Zhao Forrest
2008-04-10 7:22 ` Andi Kleen
2008-04-09 9:50 ` Arne Georg Gleditsch
2008-04-09 10:03 ` Andi Kleen
2008-04-09 10:16 ` Arne Georg Gleditsch
2008-04-09 18:02 ` Yinghai Lu
2008-04-09 13:34 ` Lennart Sorensen [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=20080409133414.GA2160@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=ak@suse.de \
--cc=andi@firstfloor.org \
--cc=arne.gleditsch@dolphinics.no \
--cc=discuss@x86-64.org \
--cc=forrest.zhao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.com \
/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
all inboxes | Powered by JetHome®