RFC make the hugetlb migration strategy consistent
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | mm: record the migration reason for struct migration_target_controlmm/ mm/ mm/ +5 more | +9 | 0 replies | |
| 2/3 | mm: hugetlb: make the hugetlb migration strategy consistentinclude/ mm/ mm/ +1 more | +30 | 6 replies | |
| 3/3 | docs: hugetlbpage.rst: add hugetlb migration descriptionDocumentation/ | +7 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/3] make the hugetlb migration strategy consistent
Hi,
As discussed in previous thread [1], there is an inconsistency when handling hugetlb migration. When handling the migration of freed hugetlb, it prevents fallback to other NUMA nodes in alloc_and_dissolve_hugetlb_folio(). However, when dealing with in-use hugetlb, it allows fallback to other NUMA nodes in alloc_hugetlb_folio_nodemask(), which can break the per-node hugetlb pool and might result in unexpected failures when node bound workloads doesn't get what is asssumed available.
This patch set tries to make the hugetlb migration strategy more clear and consistent. Please find details in each patch.
Baolin Wang (3):
mm: record the migration reason for struct migration_target_control
mm: hugetlb: make the hugetlb migration strategy consistent
docs: hugetlbpage.rst: add hugetlb migration description
Documentation/admin-guide/mm/hugetlbpage.rst | 7 +++++ include/linux/hugetlb.h | 4 +-- mm/gup.c | 1 + mm/hugetlb.c | 28 ++++++++++++++++++-- mm/internal.h | 1 + mm/memory-failure.c | 1 + mm/memory_hotplug.c | 1 + mm/mempolicy.c | 3 ++- mm/migrate.c | 3 ++- mm/page_alloc.c | 1 + mm/vmscan.c | 3 ++- 11 files changed, 46 insertions(+), 7 deletions(-)
Signature · 1 line
2.39.3