Skip to content

RFC add mTHP support for anonymous share pages

Baolin Wang linux-mm lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest5 patches 40 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5mm: memory: extend finish_fault() to support large foliomm/memory.c+18 -77 replies
2/5mm: shmem: add an 'order' parameter for shmem_alloc_hugefolio()mm/shmem.c+6 -52 replies
3/5mm: shmem: add THP validation for PMD-mapped THP related statisticsmm/shmem.c+4 -31 reply
4/5mm: shmem: add mTHP support for anonymous share pagesinclude/linux/huge_mm.h mm/huge_memory.c mm/shmem.c+74 -240 replies
5/5mm: shmem: add anonymous share mTHP countersinclude/linux/huge_mm.h mm/huge_memory.c mm/shmem.c+10 -112 replies

Reviews trailers per patch

1 of 5 patches has a Reviewed-by or Acked-by.

PatchBarry Song
1/5
2/5
3/5R-b
4/5
5/5

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [RFC PATCH 0/5] add mTHP support for anonymous share pages

Anonymous pages have already been supported for multi-size (mTHP) allocation through commit 19eaf44954df, that can allow THP to be configured through the sysfs interface located at '/sys/kernel/mm/transparent_hugepage/hugepage-XXkb/enabled'.

However, the anonymous shared pages will ignore the anonymous mTHP rule configured through the sysfs interface, and can only use the PMD-mapped THP, that is not reasonable. Many implement anonymous page sharing through mmap(MAP_SHARED | MAP_ANONYMOUS), especially in database usage scenarios, therefore, users expect to apply an unified mTHP strategy for anonymous pages, also including the anonymous shared pages, in order to enjoy the benefits of mTHP. For example, lower latency than PMD-mapped THP, smaller memory bloat than PMD-mapped THP, contiguous PTEs on ARM architecture to reduce TLB miss etc.

The primary strategy is that, the use of huge pages for anonymous shared pages still follows the global control determined by the mount option "huge=" parameter or the sysfs interface at '/sys/kernel/mm/transparent_hugepage/shmem_enabled'.
The utilization of mTHP is allowed only when the global 'huge' switch is enabled. Subsequently, the mTHP sysfs interface (/sys/kernel/mm/transparent_hugepage/hugepage-XXkb/enabled) is checked to determine the mTHP size that can be used for large folio allocation for these anonymous shared pages.

TODO:
- More testing and provide some performance data.
- Need more discussion about the large folio allocation strategy for a 'regular
file' operation created by memfd_create(), for example using ftruncate(fd) to specify the 'file' size, which need to follow the anonymous mTHP rule too?
- Do not split the large folio when share memory swap out.
- Can swap in a large folio for share memory.

Baolin Wang (5):
mm: memory: extend finish_fault() to support large folio
mm: shmem: add an 'order' parameter for shmem_alloc_hugefolio()
mm: shmem: add THP validation for PMD-mapped THP related statistics
mm: shmem: add mTHP support for anonymous share pages
mm: shmem: add anonymous share mTHP counters

 include/linux/huge_mm.h |   4 +-
 mm/huge_memory.c        |   8 ++-
 mm/memory.c             |  25 +++++++---
 mm/shmem.c              | 107 ++++++++++++++++++++++++++++++----------
 4 files changed, 108 insertions(+), 36 deletions(-)
Signature · 1 line
2.39.3