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 1284778 - packaging of glibc and malloc patches for madvise into RHEL 7
Summary: packaging of glibc and malloc patches for madvise into RHEL 7
Keywords:
Status: CLOSED DUPLICATE of bug 1284959
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Carlos O'Donell
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-24 08:35 UTC by cmilsted
Modified: 2015-11-26 10:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-26 10:58:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description cmilsted 2015-11-24 08:35:25 UTC
Description of problem:

Bugzilla to track two glibc issues and packaging of these into RHEL.

- Malloc free list cyclic fix (and followup race condition fix).
- Malloc consistent trimming fix for all arenas.


Version-Release number of selected component (if applicable):

7.2+


How reproducible:

Note that this behaviour is only triggered by certain applications and use cases, it has only been seen by a couple of customers using specific applications.

This performance loss is generally due to application design issues and triggers when the application allocates large amounts of memory, does little work, and then frees the memory. This means that as a total fraction of time the allocation and deallocation dominate. The glibc allocator in an attempt to minimize memory load on the system will trim the large deallocations and return the memory to the kernel. In these cases it is useful to increase the trimming threshold to avoid the deallocation via MADV_DONTNEED, but because trimming is only applied to the main memory arena, you can't do this for threads using non-main arenas.


Steps to Reproduce:
1. Application runs under load.
2. High sys% compared to usr% observed.
3. When tracing, notice a lot of calls to :madvise (is called from glibc heap management)

Actual results:

Before patch sys% dominates, after patch usr% dominates.

Expected results:

Sys% drops back down again and usr% dominates from the application.

Additional info:

Comment 2 cmilsted 2015-11-26 10:58:21 UTC

*** This bug has been marked as a duplicate of bug 1284959 ***


Note You need to log in before you can comment on or make changes to this bug.