RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 463279 - [LTC 6.0 FEAT] 201200:16GB huge pages for POWER
Summary: [LTC 6.0 FEAT] 201200:16GB huge pages for POWER
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: ppc64
OS: All
medium
medium
Target Milestone: alpha
: 6.0
Assignee: Kevin W Monroe
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks: 356741 RHEL6Kernel2.6.27
TreeView+ depends on / blocked
 
Reported: 2008-09-22 20:10 UTC by IBM Bug Proxy
Modified: 2010-05-06 15:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-23 22:24:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description IBM Bug Proxy 2008-09-22 20:10:40 UTC 
=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-09-16 18:24 EDT
1. Feature Overview:
Feature Id:	[201200]
a. Name of Feature:	16GB huge pages for POWER
b. Feature Description
The ability to support a page size of 16GB

2. Feature Details:
Sponsor:	PPC - P
Architectures:
ppc64

Arch Specificity: Both
Affects Core Kernel: Yes
Delivery Mechanism: Direct from community
Category:	Performance
Request Type:	Driver - Feature from IBM
d. Upstream Acceptance:	Accepted
Sponsor Priority	2
f. Severity: Medium
IBM Confidential:	no
Code Contribution:	IBM code
g. Component Version Target:	2.6.27
Performance Assistance:	yes

3. Business Case
Using 16GB pages can increase performance for systems running workloads that consume very large
amounts of memory. The target market to leverage 16GB pages includes HPC and large database
workloads. The extent of the performance increase is workload-dependent but typically 5% performance
improvements are seen when moving from 64KB pages to 16MB pages for databases. A smaller increase is
expected for 16GB pages in database applications.

For the specialized HPC system space, selected large government bids have levied the requirement for
massive amounts of dedicated memory on dedicated single-use systems. The ability to specify and
dedicate 16GB pages provides support for these highly specialized applications.  The applications
and bids are often high visibility projects for the company. In general, most HPC customers will not
require 16GB pages.

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Michael Hohnbaum, hbaum.com, 503-578-5486

Technical contact(s):
Paul Mackerras, pmac.com
Comment 1 Bill Nottingham 2008-10-01 20:51:55 UTC 
Is this code actually in 2.6.27?
Comment 2 IBM Bug Proxy 2008-10-13 22:21:06 UTC 
(In reply to comment #4)
> ------- Comment From notting 2008-10-01 16:51:55 EDT-------
> Is this code actually in 2.6.27?
>

Yes.
The actual definition of 16G pages is in
commit 91224346aa8c1cdaa660300a98e0b074a3a95030

There are other supporting patches too; as examples:

commit 658013e93eb70494f7300bc90457b09a807232a4
commit ec4b2c0c8312d1118c2acd00c89988ecf955d5cc
commit 53ba51d21d6e048424ab8aadfebdb1f25ae07b60
commit a3437870160cf2caaac6bdd76c7377a5a4145a8c

There are some bug fixes coming in 2.6.28 related to this feature, but the core code though is in 2.6.27
Comment 3 Bill Nottingham 2008-10-14 01:01:45 UTC 
Since it's in 2.6.27, and RHEL 6 will include a recent upstream kernel, setting to MODIFIED.

The feature requested has already been accepted into the upstream code base
planned for the next major release of Red Hat Enterprise Linux.

When the next milestone release of Red Hat Enterprise Linux 6 is available,
please verify that the feature requested is present and functioning as
desired.
Comment 4 IBM Bug Proxy 2009-03-02 21:31:02 UTC 
this is in 2.6.27
sha1 id: 91224346aa8c1cdaa660300a98e0b074a3a95030
Comment 5 Kevin W Monroe 2009-09-23 22:24:20 UTC 
Closing - included in Red Hat Enterprise Linux 6.
Comment 6 IBM Bug Proxy 2010-05-06 15:53:52 UTC 
------- Comment From ebmunson.com 2010-05-06 11:47 EDT-------
Verified with RHEL 6 Snap 1.
Note You need to log in before you can comment on or make changes to this bug.