lkml.org 
[lkml]   [2020]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[RFC PATCH 00/24] mm/hugetlb: Free some vmemmap pages of hugetlb page
Date
Hi all,

This patch series will free some vmemmap pages(struct page structures)
associated with each hugetlbpage when preallocated to save memory.

Nowadays we track the status of physical page frames using `struct page`
arranged in one or more arrays. And here exists one-to-one mapping between
the physical page frame and the corresponding `struct page`.

The hugetlbpage support is built on top of multiple page size support
that is provided by most modern architectures. For example, x86 CPUs
normally support 4K and 2M (1G if architecturally supported) page sizes.
Every hugetlbpage has more than one `struct page`. The 2M hugetlbpage
has 512 `struct page` and 1G hugetlbpage has 4096 `struct page`. But
in the core of hugetlbpage only uses the first 4 `struct page` to store
metadata associated with each hugetlbpage. The rest of the `struct page`
are usually read the compound_head field which are all the same value.
If we can free some struct page memory to buddy system so that We can
save a lot of memory.

When the system boot up, every 2M hugetlbpage has 512 `struct page` which
is 8 pages(sizeof(struct page) * 512 / PAGE_SIZE).

hugetlbpage struct page(8 pages) page frame(8 pages)
+-----------+ ---virt_to_page---> +-----------+ mapping to +-----------+
| | | 0 | -------------> | 0 |
| | | 1 | -------------> | 1 |
| | | 2 | -------------> | 2 |
| | | 3 | -------------> | 3 |
| | | 4 | -------------> | 4 |
| 2M | | 5 | -------------> | 5 |
| | | 6 | -------------> | 6 |
| | | 7 | -------------> | 7 |
| | +-----------+ +-----------+
| |
| |
+-----------+


When a hugetlbpage is preallocated, we can change the mapping from above to
bellow.

hugetlbpage struct page(8 pages) page frame(8 pages)
+-----------+ ---virt_to_page---> +-----------+ mapping to +-----------+
| | | 0 | -------------> | 0 |
| | | 1 | -------------> | 1 |
| | | 2 | -------------> +-----------+
| | | 3 | -----------------^ ^ ^ ^ ^
| | | 4 | -------------------+ | | |
| 2M | | 5 | ---------------------+ | |
| | | 6 | -----------------------+ |
| | | 7 | -------------------------+
| | +-----------+
| |
| |
+-----------+

The mapping of the first page(index 0) and the second page(index 1) is
unchanged. The remaining 6 pages are all mapped to the same page(index
1). So we only need 2 pages for vmemmap area and free 6 pages to the
buddy system to save memory. Why we can do this? Because the content
of the remaining 7 pages are usually same except the first page.

When a hugetlbpage is freed to the buddy system, we should allocate 6
pages for vmemmap pages and restore the previous mapping relationship.

If we uses the 1G hugetlbpage, we can save 4095 pages. This is a very
substantial gain. On our server, run some SPDK applications which will
use 300GB hugetlbpage. With this feature enabled, we can save 4797MB
memory.

Muchun Song (24):
mm/memory_hotplug: Move bootmem info registration API to
bootmem_info.c
mm/memory_hotplug: Move {get,put}_page_bootmem() to bootmem_info.c
mm/hugetlb: Introduce a new config HUGETLB_PAGE_FREE_VMEMMAP
mm/hugetlb: Register bootmem info when
CONFIG_HUGETLB_PAGE_FREE_VMEMMAP
mm/hugetlb: Introduce nr_free_vmemmap_pages in the struct hstate
mm/hugetlb: Introduce pgtable allocation/freeing helpers
mm/hugetlb: Add freeing unused vmemmap pages support for x86
mm/bootmem_info: Introduce {free,prepare}_vmemmap_page()
x86/mm: Introduce VMEMMAP_SIZE/VMEMMAP_END macro
mm/hugetlb: Free the vmemmap pages associated with each hugetlb page
mm/hugetlb: Add vmemmap_pmd_huge macro for x86
mm/hugetlb: Defer freeing of hugetlb pages
mm/hugetlb: Allocate the vmemmap pages associated with each hugetlb
page
mm/hugetlb: Introduce remap_huge_page_pmd_vmemmap helper
mm/hugetlb: Use PG_slab to indicate split pmd
mm/hugetlb: Support freeing vmemmap pages of gigantic page
mm/hugetlb: Add a BUILD_BUG_ON to check if struct page size is a power
of two
mm/hugetlb: Clear PageHWPoison on the non-error memory page
mm/hugetlb: Flush work when dissolving hugetlb page
mm/hugetlb: Add a kernel parameter hugetlb_free_vmemmap
mm/hugetlb: Merge pte to huge pmd only for gigantic page
mm/hugetlb: Implement vmemmap_pmd_mkhuge macro
mm/hugetlb: Gather discrete indexes of tail page
mm/hugetlb: Add BUILD_BUG_ON to catch invalid usage of tail struct
page

.../admin-guide/kernel-parameters.txt | 9 +
Documentation/admin-guide/mm/hugetlbpage.rst | 3 +
arch/x86/include/asm/hugetlb.h | 20 +
arch/x86/include/asm/pgtable_64_types.h | 8 +
arch/x86/mm/init_64.c | 5 +-
fs/Kconfig | 15 +
include/linux/bootmem_info.h | 65 ++
include/linux/hugetlb.h | 64 ++
include/linux/hugetlb_cgroup.h | 15 +-
include/linux/memory_hotplug.h | 27 -
mm/Makefile | 1 +
mm/bootmem_info.c | 125 +++
mm/hugetlb.c | 834 +++++++++++++++++-
mm/memory_hotplug.c | 116 ---
mm/sparse.c | 1 +
15 files changed, 1143 insertions(+), 165 deletions(-)
create mode 100644 include/linux/bootmem_info.h
create mode 100644 mm/bootmem_info.c

--
2.20.1

\
 
 \ /
  Last update: 2020-09-16 02:46    [W:0.243 / U:1.900 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site