| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 26 Oct 2020 22:50:55 +0800
From: Muchun Song <songmuchun@...edance.com>
To: corbet@....net, mike.kravetz@...cle.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, x86@...nel.org, hpa@...or.com,
dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org,
viro@...iv.linux.org.uk, akpm@...ux-foundation.org,
paulmck@...nel.org, mchehab+huawei@...nel.org,
pawan.kumar.gupta@...ux.intel.com, rdunlap@...radead.org,
oneukum@...e.com, anshuman.khandual@....com, jroedel@...e.de,
almasrymina@...gle.com, rientjes@...gle.com, willy@...radead.org
Cc: duanxiongchun@...edance.com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org,
Muchun Song <songmuchun@...edance.com>
Subject: [PATCH v2 00/19] Free some vmemmap pages of hugetlb page
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 pages(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 pages(8 pages) page frame(8 pages)
+-----------+ ---virt_to_page---> +-----------+ mapping to +-----------+
| | | 0 | -------------> | 0 |
| | | 1 | -------------> | 1 |
| | | 2 | -------------> +-----------+
| | | 3 | -----------------^ ^ ^ ^ ^
| | | 4 | -------------------+ | | |
| 2M | | 5 | ---------------------+ | |
| | | 6 | -----------------------+ |
| | | 7 | -------------------------+
| | +-----------+
| |
| |
+-----------+
For tail pages, the value of compound_dtor is the same. So we can reuse
first page of tail page structs. We map the virtual addresses of the
remaining 6 pages of tail page structs to the first tail page struct,
and then free these 6 pages. Therefore, we need to reserve at least 2
pages as vmemmap areas.
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/QEMU applications which
will use 1000GB hugetlbpage. With this feature enabled, we can save
~16GB(1G hugepage)/~11GB(2MB hugepage) memory.
changelog in v2:
1. Fix do not call dissolve_compound_page in alloc_huge_page_vmemmap().
2. Fix some typo and code style problems.
3. Remove unused handle_vmemmap_fault().
4. Merge some commits to one commit suggested by Mike.
Muchun Song (19):
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: Introduce nr_free_vmemmap_pages in the struct hstate
mm/hugetlb: Introduce pgtable allocation/freeing helpers
mm/bootmem_info: Introduce {free,prepare}_vmemmap_page()
mm/hugetlb: Free the vmemmap pages associated with each hugetlb page
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: 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 | 16 +
include/linux/bootmem_info.h | 65 ++
include/linux/hugetlb.h | 50 ++
include/linux/hugetlb_cgroup.h | 15 +-
include/linux/memory_hotplug.h | 27 -
mm/Makefile | 1 +
mm/bootmem_info.c | 125 +++
mm/hugetlb.c | 795 +++++++++++++++++-
mm/memory_hotplug.c | 116 ---
mm/sparse.c | 1 +
15 files changed, 1091 insertions(+), 165 deletions(-)
create mode 100644 include/linux/bootmem_info.h
create mode 100644 mm/bootmem_info.c
--
2.20.1
Powered by blists - more mailing lists