Red Hat Bugzilla – Bug 463613
[LTC 6.0 FEAT] 201194:libhugetlbfs package update
Last modified: 2010-05-27 04:48:04 EDT
Emily J. Ratliff <email@example.com> - 2008-09-16 18:07 EDT
1. Feature Overview:
Feature Id: 
a. Name of Feature: libhugetlbfs package update
b. Feature Description
Place holder for pulling latest version at time of code freeze if any bugfixes/features from
upstream end up being needed.
2. Feature Details:
Arch Specificity: Purely Common Code
Delivery Mechanism: Direct from community
Request Type: Package - Update Version
d. Upstream Acceptance: Accepted
Sponsor Priority 2
f. Severity: Medium
IBM Confidential: no
Code Contribution: IBM code
g. Component Version Target: Latest version
Performance Assistance: yes
3. Business Case
libhugetlbfs provides substantial performance improvements for certain workloads so it functioning
optimally enables Linux HPC sales that would previously go to other operating systems.
4. Primary contact at Red Hat:
5. Primary contacts at Partner:
Project Management Contact:
Michael Hohnbaum, firstname.lastname@example.org, 503-578-5486
Adam Litke, email@example.com
Nishanth Aravamudan, firstname.lastname@example.org
Pat Gaughen, email@example.com
Mind that a new version will be pulled at feature freeze, not code freeze (maybe just a matter of nomenclature). Ping me when that version is available.
libhugetlbfs 2.2 should be packaged in Fedora. The three RPMs are
Please pull all three packages. Thanks
As version 2.2 is now in Fedora, this should get pulled for RHEL6.
------- Comment From firstname.lastname@example.org 2009-09-09 23:54 EDT-------
We need to keep this bug opened until we test it in rhel6 since this is a rhel6 feature.
------- Comment From email@example.com 2009-09-09 23:57 EDT-------
move to accept based on its external status (Modified)
IBM is signed up to test and provide feedback
Fixed in 'libhugetlbfs-2.6-2.el6', included in compose 'RHEL6.0-20091029.0'.
Moving to ON_QA.
------- Comment From firstname.lastname@example.org 2009-11-16 19:13 EDT-------
These are also expected failures, they are testing the old relinking method. These tests should only be used to determine is the old method works with a particular compiler/binutils combination. As long as the new linker method worked (and it looks like it did) these errors can be ignored.
------- Comment From email@example.com 2010-05-06 11:46 EDT-------
Verified with RHEL 6 Snap 1. There is a small problem with the test suite that does not affect the library or any of the utilities. I will open a separate bu with a patch to fix the issue but this should not stand in the way of the package update.
Thank you for the verification.