Skip to contentSkip to conversation

docs-hugetlbpagerst-add-hugetlb-migration-description.patch removed from -mm tree

merged mm-stable Andrew Morton 1 participant 1 message Apr 26, 2024

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The quilt patch titled
Subject: docs: hugetlbpage.rst: add hugetlb migration description
has been removed from the -mm tree. Its filename was
docs-hugetlbpagerst-add-hugetlb-migration-description.patch

This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Baolin Wang <[email protected]>
Subject: docs: hugetlbpage.rst: add hugetlb migration description
Date: Wed, 6 Mar 2024 18:13:28 +0800

Add some description of the hugetlb migration strategy.

---

 Documentation/admin-guide/mm/hugetlbpage.rst |    7 +++++++
 1 file changed, 7 insertions(+)
Documentation/admin-guide/mm/hugetlbpage.rst renamed from Documentation/admin-guide/mm/hugetlbpage.rst~docs-hugetlbpagerst-add-hugetlb-migration-description +7 -0
@@ -376,6 +376,13 @@ Note that the number of overcommit and r
 as we don't know until fault time, when the faulting task's mempolicy is
 applied, from which node the huge page allocation will be attempted.
 
+The hugetlb may be migrated between the per-node hugepages pool in the following
+scenarios: memory offline, memory failure, longterm pinning, syscalls(mbind,
+migrate_pages and move_pages), alloc_contig_range() and alloc_contig_pages().
+Now only memory offline, memory failure and syscalls allow fallbacking to allocate
+a new hugetlb on a different node if the current node is unable to allocate during
+hugetlb migration, that means these 3 cases can break the per-node hugepages pool.
+
 .. _using_huge_pages:
 
 Using Huge Pages

_

Patches currently in -mm which might be from [email protected] are

mm-page_alloc-allowing-mthp-compaction-to-capture-the-freed-page-directly.patch