From: Rik van Riel <riel@redhat.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: Re: 128 GiB memory question-- kernel only sees 64GiB?
Date: Tue, 22 Jul 2008 17:14:41 -0400 [thread overview]
Message-ID: <20080722171441.6daee243@bree.surriel.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0807221655140.11681@p34.internal.lan>
On Tue, 22 Jul 2008 16:55:32 -0400 (EDT)
Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> On Tue, 22 Jul 2008, Rik van Riel wrote:
>
> > On Tue, 22 Jul 2008 10:21:44 -0400 (EDT)
> > Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> >
> >> To be able to utilize 128 GiB of memory on a host, does one need to enable
> >> NUMA support? Currently only 64 GiB is showing up.
> >
> > How much memory does the BIOS say the system has?
> Asked them.
>
> >
> > Can you get the e820 memory map (from early boot up) of the systems?
> Probably can't get this.
It looks roughly like this:
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 0000000000100000 - 00000000bfb50000 (usable)
BIOS-e820: 00000000bfb50000 - 00000000bfb66000 (reserved)
BIOS-e820: 00000000bfb66000 - 00000000bfb85c00 (ACPI data)
BIOS-e820: 00000000bfb85c00 - 00000000c0000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fe000000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000440000000 (usable)
Getting this info will be very useful.
--
All rights reversed.
prev parent reply other threads:[~2008-07-22 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 14:21 128 GiB memory question-- kernel only sees 64GiB? Justin Piszcz
2008-07-22 14:28 ` Peter Zijlstra
2008-07-22 20:55 ` Justin Piszcz
2008-07-23 8:21 ` Yinghai Lu
2008-07-22 14:43 ` Rik van Riel
2008-07-22 20:55 ` Justin Piszcz
2008-07-22 21:14 ` Rik van Riel [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=20080722171441.6daee243@bree.surriel.com \
--to=riel@redhat.com \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@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