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 819965 - THP page migration
Summary: THP page migration
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Aristeu Rozanski
QA Contact: Li Wang
URL:
Whiteboard:
Depends On:
Blocks: 817917 919431 1032535 1032538 1071730 1296180 1394638 1469551
TreeView+ depends on / blocked
 
Reported: 2012-05-08 18:28 UTC by Rik van Riel
Modified: 2023-08-08 02:22 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-20 20:44:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rik van Riel 2012-05-08 18:28:49 UTC
Description of problem:

Currently, page migration breaks 2MB pages into 4kB pages, which then have to be reassembled again at the destination. This negates a lot of the performance benefits of doing NUMA relocations in the first place.

2MB transparent hugepages should stay intact across page migration.

We can use the same bit that is used to protect 2MB->4kB and 4kB->2MB transitions to block out page accesses during a 2MB->2MB transition.

Comment 5 Johannes Weiner 2013-09-03 21:16:09 UTC
THP-preserving migration is included in the NUMA balancing code.

Comment 6 Rik van Riel 2013-11-20 13:45:13 UTC
Johannes,

if you look unmap_and_move, which is indirectly called from sys_migrate_pages, you will see that it does NOT preserve THP on migration. There is a reason this bug was opened separately.

Comment 7 Johannes Weiner 2013-11-21 17:03:02 UTC
(In reply to Rik van Riel from comment #6)
> Johannes,
> 
> if you look unmap_and_move, which is indirectly called from
> sys_migrate_pages, you will see that it does NOT preserve THP on migration.
> There is a reason this bug was opened separately.

My bad, I was under the assumption this was to track the side-project of adding THP-preserving migration to AutoNUMA.

I'll dig up the patches.

Comment 8 Ludek Smid 2014-06-26 10:42:53 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.

Comment 9 Ludek Smid 2014-06-26 11:16:36 UTC
The comment above is incorrect. The correct version is bellow.
I'm sorry for any inconvenience.
---------------------------------------------------------------

This request was NOT resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you need
to escalate this bug.


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