From: Tom Sightler <ttsig@tuxyturvy.com>
To: Buddy Lumpkin <b.lumpkin@comcast.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Large page support in the Linux Kernel?
Date: Sat, 01 May 2004 12:15:50 -0400 [thread overview]
Message-ID: <1083428150.3810.18.camel@localhost.localdomain> (raw)
In-Reply-To: <S262103AbUEAJXe/20040501092334Z+498@vger.kernel.org>
On Sat, 2004-05-01 at 05:28, Buddy Lumpkin wrote:
> Lastly, I know I have mentioned Oracle and Solaris a lot. Please don't flame
> me for this, I think the points I am trying to make are reasonable.
The only reason to be flamed is that you didn't seem to do much research
before posting. RHEL 2.1 has supported a feature called "BigPages"
specifically used for Oracle for quite a while. Good documentation on
how to set this up can be found from Redhat, Oracle, and a quick Google
search.
See
http://www.puschitz.com/TuningLinuxForOracle.shtml#UsingLargeMemoryPages
for instructions on how to set it up. Basically you pass a kernel
parameter to tell the system how much memory to allocate as big pages
and the kernel reserves this memory for it's use.
RHEL 3.0 and current 2.6 kernel support a newer variant called Hugetlb
which seems similar from a user perspective but I'm not sure of the
implementation details. It more dynamic, you can decrease or increase
memory allocated to Hugetlb's via /proc athough, you can't always grow
it (the kernel has to be able to allocate contiguous segments to grow
the system). I'm not aware of any instruction in the community about
how to set this up, but Oracle's Metalink provides complete
instructions. I'm already using it on my five production Oracle
instances and have had no problems with it.
Later,
Tom
next prev parent reply other threads:[~2004-05-01 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 9:28 Large page support in the Linux Kernel? Buddy Lumpkin
2004-05-01 10:36 ` Paul Jackson
2004-05-02 4:45 ` Buddy Lumpkin
2004-05-01 16:15 ` Tom Sightler [this message]
2004-05-01 23:22 ` 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=1083428150.3810.18.camel@localhost.localdomain \
--to=ttsig@tuxyturvy.com \
--cc=b.lumpkin@comcast.net \
--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