From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
linux-kernel@vger.kernel.org, "Alan Piszcz" <ap@solarrain.com>
Subject: Re: 128 GiB memory question-- kernel only sees 64GiB?
Date: Wed, 23 Jul 2008 01:21:01 -0700 [thread overview]
Message-ID: <86802c440807230121o584d2573g8ec4d4fde857aa3b@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0807221654480.11681@p34.internal.lan>
On Tue, Jul 22, 2008 at 1:55 PM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>
>
> On Tue, 22 Jul 2008, Peter Zijlstra wrote:
>
>> On Tue, 2008-07-22 at 10:21 -0400, Justin Piszcz wrote:
>>>
>>> Hello,
>>>
>>> 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.
>>>
>>> As far as machine name/motherboard type, I do not have this information
>>> currently but I am told there are one or two of these boxes are running
>>> CentOS 5.x and/or RHEL5/AS.
>>
>> Sounds like you need to bug RH with that ;-)
>>
>>> Is there something special you need to do to utilize all 128 GiB of
>>> memory?
>>
>> Does a recent kernel work for you? Also, you could at the very least
>> have mentioned your machine architecture; is it x86_64, ia64 or ppc64?
>>
>
> Sun X4600, will find out if they are running the right kernel and also check
> the BIOS, thanks.
so you are using 32 bit kernel?
uname -a
could tell arch
YH
next prev parent reply other threads:[~2008-07-23 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 14:21 Justin Piszcz
2008-07-22 14:28 ` Peter Zijlstra
2008-07-22 20:55 ` Justin Piszcz
2008-07-23 8:21 ` Yinghai Lu [this message]
2008-07-22 14:43 ` Rik van Riel
2008-07-22 20:55 ` Justin Piszcz
2008-07-22 21:14 ` Rik van Riel
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=86802c440807230121o584d2573g8ec4d4fde857aa3b@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®