On 07.12.20 14:11, Muchun Song wrote:
> On Mon, Dec 7, 2020 at 8:36 PM David Hildenbrand <david@xxxxxxxxxx> wrote:
>>
>> On 30.11.20 16:18, Muchun Song wrote:
>>> Every HugeTLB has more than one struct page structure. The 2M HugeTLB
>>> has 512 struct page structure and 1G HugeTLB has 4096 struct page
>>> structures. We __know__ that we only use the first 4(HUGETLB_CGROUP_MIN_ORDER)
>>> struct page structures to store metadata associated with each HugeTLB.
>>>
>>> There are a lot of struct page structures(8 page frames for 2MB HugeTLB
>>> page and 4096 page frames for 1GB HugeTLB page) associated with each
>>> HugeTLB page. For tail pages, the value of compound_head is the same.
>>> So we can reuse first page of tail page structures. We map the virtual
>>> addresses of the remaining pages of tail page structures to the first
>>> tail page struct, and then free these page frames. Therefore, we need
>>> to reserve two pages as vmemmap areas.
>>>
>>> So we introduce a new nr_free_vmemmap_pages field in the hstate to
>>> indicate how many vmemmap pages associated with a HugeTLB page that we
>>> can free to buddy system.
>>>
>>> Signed-off-by: Muchun Song <songmuchun@xxxxxxxxxxxxx>
>>> Acked-by: Mike Kravetz <mike.kravetz@xxxxxxxxxx>
>>> ---
>>> include/linux/hugetlb.h | 3 ++
>>> mm/Makefile | 1 +
>>> mm/hugetlb.c | 3 ++
>>> mm/hugetlb_vmemmap.c | 129 ++++++++++++++++++++++++++++++++++++++++++++++++
>>> mm/hugetlb_vmemmap.h | 20 ++++++++
>>> 5 files changed, 156 insertions(+)
>>> create mode 100644 mm/hugetlb_vmemmap.c
>>> create mode 100644 mm/hugetlb_vmemmap.h
>>>
>>> diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
>>> index ebca2ef02212..4efeccb7192c 100644
>>> --- a/include/linux/hugetlb.h
>>> +++ b/include/linux/hugetlb.h
>>> @@ -492,6 +492,9 @@ struct hstate {
>>> unsigned int nr_huge_pages_node[MAX_NUMNODES];
>>> unsigned int free_huge_pages_node[MAX_NUMNODES];
>>> unsigned int surplus_huge_pages_node[MAX_NUMNODES];
>>> +#ifdef CONFIG_HUGETLB_PAGE_FREE_VMEMMAP
>>> + unsigned int nr_free_vmemmap_pages;
>>> +#endif
>>> #ifdef CONFIG_CGROUP_HUGETLB
>>> /* cgroup control files */
>>> struct cftype cgroup_files_dfl[7];
>>> diff --git a/mm/Makefile b/mm/Makefile
>>> index ed4b88fa0f5e..056801d8daae 100644
>>> --- a/mm/Makefile
>>> +++ b/mm/Makefile
>>> @@ -71,6 +71,7 @@ obj-$(CONFIG_FRONTSWAP) += frontswap.o
>>> obj-$(CONFIG_ZSWAP) += zswap.o
>>> obj-$(CONFIG_HAS_DMA) += dmapool.o
>>> obj-$(CONFIG_HUGETLBFS) += hugetlb.o
>>> +obj-$(CONFIG_HUGETLB_PAGE_FREE_VMEMMAP) += hugetlb_vmemmap.o
>>> obj-$(CONFIG_NUMA) += mempolicy.o
>>> obj-$(CONFIG_SPARSEMEM) += sparse.o
>>> obj-$(CONFIG_SPARSEMEM_VMEMMAP) += sparse-vmemmap.o
>>> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
>>> index 1f3bf1710b66..25f9e8e9fc4a 100644
>>> --- a/mm/hugetlb.c
>>> +++ b/mm/hugetlb.c
>>> @@ -42,6 +42,7 @@
>>> #include <linux/userfaultfd_k.h>
>>> #include <linux/page_owner.h>
>>> #include "internal.h"
>>> +#include "hugetlb_vmemmap.h"
>>>
>>> int hugetlb_max_hstate __read_mostly;
>>> unsigned int default_hstate_idx;
>>> @@ -3206,6 +3207,8 @@ void __init hugetlb_add_hstate(unsigned int order)
>>> snprintf(h->name, HSTATE_NAME_LEN, "hugepages-%lukB",
>>> huge_page_size(h)/1024);
>>>
>>> + hugetlb_vmemmap_init(h);
>>> +
>>> parsed_hstate = h;
>>> }
>>>
>>> diff --git a/mm/hugetlb_vmemmap.c b/mm/hugetlb_vmemmap.c
>>> new file mode 100644
>>> index 000000000000..51152e258f39
>>> --- /dev/null
>>> +++ b/mm/hugetlb_vmemmap.c
>>> @@ -0,0 +1,129 @@
>>> +// SPDX-License-Identifier: GPL-2.0
>>> +/*
>>> + * Free some vmemmap pages of HugeTLB
>>> + *
>>> + * Copyright (c) 2020, Bytedance. All rights reserved.
>>> + *
>>> + * Author: Muchun Song <songmuchun@xxxxxxxxxxxxx>
>>> + *
>>> + * The struct page structures (page structs) are used to describe a physical
>>> + * page frame. By default, there is a one-to-one mapping from a page frame to
>>> + * it's corresponding page struct.
>>> + *
>>> + * The HugeTLB pages consist of multiple base page size pages and is supported
>>> + * by many architectures. See hugetlbpage.rst in the Documentation directory
>>> + * for more details. On the x86 architecture, HugeTLB pages of size 2MB and 1GB
>>> + * are currently supported. Since the base page size on x86 is 4KB, a 2MB
>>> + * HugeTLB page consists of 512 base pages and a 1GB HugeTLB page consists of
>>> + * 4096 base pages. For each base page, there is a corresponding page struct.
>>> + *
>>> + * Within the HugeTLB subsystem, only the first 4 page structs are used to
>>> + * contain unique information about a HugeTLB page. HUGETLB_CGROUP_MIN_ORDER
>>> + * provides this upper limit. The only 'useful' information in the remaining
>>> + * page structs is the compound_head field, and this field is the same for all
>>> + * tail pages.
>>> + *
>>> + * By removing redundant page structs for HugeTLB pages, memory can returned to
>>> + * the buddy allocator for other uses.
>>> + *
>>> + * When the system boot up, every 2M HugeTLB has 512 struct page structs which
>>> + * size is 8 pages(sizeof(struct page) * 512 / PAGE_SIZE).
>>
>>
>> You should try to generalize all descriptions regarding differing base
>> page sizes. E.g., arm64 supports 4k, 16k, and 64k base pages.
>
> Will do. Thanks.
>
>>
>> [...]
>>
>>> @@ -0,0 +1,20 @@
>>> +// SPDX-License-Identifier: GPL-2.0
>>> +/*
>>> + * Free some vmemmap pages of HugeTLB
>>> + *
>>> + * Copyright (c) 2020, Bytedance. All rights reserved.
>>> + *
>>> + * Author: Muchun Song <songmuchun@xxxxxxxxxxxxx>
>>> + */
>>> +#ifndef _LINUX_HUGETLB_VMEMMAP_H
>>> +#define _LINUX_HUGETLB_VMEMMAP_H
>>> +#include <linux/hugetlb.h>
>>> +
>>> +#ifdef CONFIG_HUGETLB_PAGE_FREE_VMEMMAP
>>> +void __init hugetlb_vmemmap_init(struct hstate *h);
>>> +#else
>>> +static inline void hugetlb_vmemmap_init(struct hstate *h)
>>> +{
>>> +}
>>> +#endif /* CONFIG_HUGETLB_PAGE_FREE_VMEMMAP */
>>> +#endif /* _LINUX_HUGETLB_VMEMMAP_H */
>>>
>>
>> This patch as it stands is rather sub-optimal. I mean, all it does is
>> add documentation and print what could be done.
>>
>> Can we instead introduce the basic infrastructure and enable it via this
>> patch on top, where we glue all the pieces together? Or is there
>> something I am missing?
>
> Maybe we can make the config of CONFIG_HUGETLB_PAGE_FREE_VMEMMAP
> default n in the Kconfig. When everything is ready, then make it
> default to y. Right?
I think it can make sense to introduce the
CONFIG_HUGETLB_PAGE_FREE_VMEMMAP option first if necessary for other
patches. But I think the the documentation and the dummy call should
rather be moved to the end of the series where you glue everything you
introduced together and officially unlock the feature. Others might
disagree :)
BTW, I'm planning on reviewing the other parts of this series, I'm just
fairly busy, so it might take a while (I think we're targeting 5.12
either way as the 5.11 merge window will start fairly soon).
--
Thanks,
David / dhildenb
