SCIENTIFIC-LINUX-USERS Archives

January 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Akemi Yagi <[log in to unmask]>
Reply To:
Akemi Yagi <[log in to unmask]>
Date:
Fri, 29 Jan 2010 13:59:13 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
On Fri, Jan 29, 2010 at 9:25 AM, Connie Sieh <[log in to unmask]> wrote:

> Yes Oracle gets the same rules as everyone else.  Note that there is the
> concept of HUGEPAGES which a application can use which may help with this ,
>  not sure if Oracle uses that.  I think there are some Oracle tech notes
> that cover this topic.

While we are still talking about the memory stuff ... there is an
interesting issue about "4G of addressable memory per process" in the
upstream bugzilla[1]. Here's an excerpt:

"Physical Address Extension allows x86 processors to address up to
64GB of physical RAM, but due to differences between the Red Hat Enterprise
Linux 4 and 5 kernels, only Red Hat Enterprise Linux 4 (with kernel-hugemem
package) is able to reliably address all 64GB of memory. Additionally, the Red
Hat Enterprise Linux 5 PAE variant does not allow 4G of addressable memory
per-process like the Red Hat Enterprise Linux 4 kernel-hugemem variant does.
However, the x86_64 kernel does not suffer from any of these limitations, and
is the suggested Red Hat Enterprise Linux 5 architecture to use with
large-memory systems."

[1] https://bugzilla.redhat.com/show_bug.cgi?id=241314

Akemi

ATOM RSS1 RSS2