From: "Zhao Forrest" <forrest.zhao@gmail.com>
To: discuss@x86-64.org, linux-kernel@vger.kernel.org
Cc: yhlu.kernel@gmail.com, mingo@elte.hu, ak@suse.de
Subject: Does Linux have plan to support memory hole remapping?
Date: Wed, 9 Apr 2008 15:54:01 +0800 [thread overview]
Message-ID: <ac8af0be0804090054w47f48ddel387d80a0331d16e1@mail.gmail.com> (raw)
Hi experts,
I ask this because I run kernel 2.6.25-rc8 on a x64 system with 32GB
physical memory, and kernel only use (32GB-512MB) physical memory. See
below related information:
E820 table:
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 0000000000098c00 (usable)
BIOS-e820: 0000000000098c00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000dffa0000 (usable)
BIOS-e820: 00000000dffae000 - 00000000dffb0000 type 9
BIOS-e820: 00000000dffb0000 - 00000000dffbe000 (ACPI data)
BIOS-e820: 00000000dffbe000 - 00000000dfff0000 (ACPI NVS)
BIOS-e820: 00000000dfff0000 - 00000000dfffe000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ff700000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000820000000 (usable)
/proc/mtrr:
reg00: base=0x00000000 ( 0MB), size=32768MB: write-back, count=1
reg01: base=0x800000000 (32768MB), size= 512MB: write-back, count=1
reg02: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1
/proc/meminfo:
MemTotal: 33010240 kB
MemFree: 32715924 kB
Buffers: 1624 kB
Cached: 31412 kB
SwapCached: 0 kB
Active: 22348 kB
Inactive: 19728 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 9120 kB
Mapped: 6408 kB
Slab: 24828 kB
SReclaimable: 8004 kB
SUnreclaim: 16824 kB
PageTables: 1296 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 16505120 kB
Committed_AS: 16556 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 73524 kB
VmallocChunk: 34359664507 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
As we can see from above information that the physical memory in system
is 32768MB(32GB). However OS is only using about
(32768-512)MB(MemTotal: 33010240 kB). Does this mean that this
linux kernel can't use the physical memory remapped
from (4G-512M, 4G) to (32G, 32G+512M)?
Thanks,
Forrest
next reply other threads:[~2008-04-09 7:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 7:54 Zhao Forrest [this message]
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
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=ac8af0be0804090054w47f48ddel387d80a0331d16e1@mail.gmail.com \
--to=forrest.zhao@gmail.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--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®