From: Tobias Diedrich <ranma+xen@tdiedrich.de>
To: xen-users@lists.xensource.com
Cc: linux-kernel@vger.kernel.org
Subject: [Xen-users] 3.0.0-rc2: Xen: High amount of kernel "reserved" memory, about 33% in 256MB DOMU
Date: Mon, 13 Jun 2011 22:50:03 +0200 [thread overview]
Message-ID: <20110613205003.GD20616@yumi.tdiedrich.de> (raw)
Hi,
another issue I'm seeing with 3.0-rc2 and Xen is that there is an
unexpectedly high amount of kernel reserved memory.
I suspect that Linux allocates page table entries and corresponding
data structures for the whole 6GB areas of the provided 'physical
RAM map' even though it has rather big unusable holes in it.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 000000000009f000 (usable)
[ 0.000000] Xen: 000000000009f000 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000010000000 (usable)
[ 0.000000] Xen: 0000000010000000 - 000000007fef0000 (unusable)
[ 0.000000] Xen: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
[ 0.000000] Xen: 000000007fef3000 - 000000007ff00000 (ACPI data)
[ 0.000000] Xen: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] Xen: 0000000100000000 - 000000016fef0000 (usable)
On DOMUs I can 'fix' this by adding 'memmap=0x800000$0x100000000' to
the kernel command line, which changes
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 00000000000a0000 (usable)
[ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000010000000 (usable)
[ 0.000000] Xen: 0000000100000000 - 0000000100800000 (usable)
[...]
[ 0.000000] Memory: 176356k/4202496k available (6096k kernel code, 3932608k absent, 93532k reserved, 4785k data, 572k init)
to
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 00000000000a0000 (usable)
[ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 0000000010000000 (usable)
[ 0.000000] Xen: 0000000100000000 - 0000000100800000 (usable)
[...]
[ 0.000000] user-defined physical RAM map:
[ 0.000000] user: 0000000000000000 - 00000000000a0000 (usable)
[ 0.000000] user: 00000000000a0000 - 0000000000100000 (reserved)
[ 0.000000] user: 0000000000100000 - 0000000010000000 (usable)
[...]
[ 0.000000] user: 0000000100000000 - 0000000100800000 (reserved)
[ 0.000000] Memory: 244212k/262144k available (6096k kernel code, 448k absent, 17484k reserved, 4785k data, 572k init)
With 66MB of usable memory out of 256MB recovered and a reasonable
93% of memory usable for userspace instead of just 67%.
I also see this on my 256MB DOM0:
Memory: 146536k/6028224k available (6122k kernel code, 3932612k absent, 1949076k reserved, 4761k data, 576k init)
Only 143MB out of 256MB allocated for DOM0 is usable for userspace.
Regards,
--
Tobias PGP: http://8ef7ddba.uguu.de
next reply other threads:[~2011-06-13 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 20:50 Tobias Diedrich [this message]
2011-06-13 21:59 ` Konrad Rzeszutek Wilk
2011-06-14 0:10 ` Tobias Diedrich
2011-06-14 19:48 ` 3.0.0-rc2: Xen: High amount of kernel "reserved" memory, about 33% in 256MB DOMU [workaround included] Konrad Rzeszutek Wilk
2011-06-14 21:37 ` Tobias Diedrich
2011-06-14 21:14 ` [Xen-users] 3.0.0-rc2: Xen: High amount of kernel "reserved" memory, about 33% in 256MB DOMU Tobias Diedrich
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=20110613205003.GD20616@yumi.tdiedrich.de \
--to=ranma+xen@tdiedrich.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-users@lists.xensource.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®