Hey, thanks for the testing steps.
I tried applying these patches on 5.11 source tree. These patches were applied
on top of the x86 patch, which worked fine. But in this case we don't see the
same improvements in our testing. We made sure we set
CONFIG_HUGETLB_PAGE_FREE_VMEMMAP=y in our .config file.
Are we missing any more configuration settings to get this patch to work on
ARM? Can you please help with general troubleshooting steps to debug what could
be going wrong.
On 11/03/21, 11:32 AM, "Chen Huang" <chenhua...@huawei.com> wrote:
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you can confirm the sender and know the
content is safe.
在 2021/3/11 13:00, Bodeddula, Balasubramaniam 写道:
> Chen, is your testing steps documented somewhere, can you please point us
to the same. I followed some steps for testing the x86 patches, just wanted to
make sure I am covering your tests as well. We are actively working on building
and testing these patches for ARM.
>
> On 11/03/21, 9:44 AM, "Chen Huang" <chenhua...@huawei.com> wrote:
>
> CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you can confirm the sender and know
the content is safe.
>
>
>
> 在 2021/3/10 15:15, Muchun Song 写道:
> > This patchset is based on the series of "Free some vmemmap pages of
HugeTLB
> > page". More details can refer to the below link.
> >
> >
https://lkml.kernel.org/r/20210308102807.59745-1-songmuc...@bytedance.com
> >
> > I often received some feedback (We want to test this feature on
arm64) before.
> > Because the previous code has been reviewed for 18 versions and is
merged
> > into mm tree, I think that it is time to release this patchset. If
you want
> > to test then you can start now :-). And I also hope someone can
review this.
> >
> > Thanks.
> >
> > Muchun Song (3):
> > mm: bootmem_info: mark register_page_bootmem_info_section __init
> > mm: hugetlb: introduce arch_free_vmemmap_page
> > arm64: mm: hugetlb: add support for free vmemmap pages of HugeTLB
> >
> > arch/arm64/mm/mmu.c | 5 +++++
> > arch/x86/mm/init_64.c | 5 +++++
> > fs/Kconfig | 4 ++--
> > mm/bootmem_info.c | 4 ++--
> > mm/sparse-vmemmap.c | 9 +++++++--
> > 5 files changed, 21 insertions(+), 6 deletions(-)
> >
>
> Tested-by: Chen Huang <chenhua...@huawei.com>
>
> I have tested the patch and the result is same as the last time.
>
The test work is that: I set the total memory of 40G, and use 10G for
hugepages.
First I reserve 10G hugepages from the command line and the result is that:
------------------------------------------------------------------------------------------------
2M page | 1G page
|
----------------------|------------------------|----------------------|------------------------|
enable | disable | enable |
disable |
----------------------|------------------------|----------------------|------------------------|
total | used | free | total | used | free |total | used | free |
total | used | free |
39,697 | 10279 |29,415| 39580 | 10279 | 29,297|39,739 | 10279 |29,455|
39580 | 10279 | 29,296|
------------------------------------------------------------------------------------------------
For 2M hugepage, we can save 118M memory which is correspoinding to the
expected 120M memory.
For 1G hugepage, we can save 159M memory which is correspoinding to the
expected 160M memory.
Then I alloc 10G hugepages using "echo XX >
/sys/kernel/mm/hugepages/hugepages-XXkB/nr_hugepages",
and get the result:
------------------------------------------------------------------------------------------------
2M page | 1G page
|
----------------------|------------------------|----------------------|------------------------|
enable | disable | enable |
disable |
----------------------|------------------------|----------------------|------------------------|
total | used | free | total | used | free |total | used | free |
total | used | free |
39,699 | 10279 |29,415| 39580 | 10279 | 29,297|39,739 | 10279 |29,455|
39580 | 10279 | 29,296|
------------------------------------------------------------------------------------------------
For 2M hugepage, we can save 118M memory which is correspoinding to the
expected 120M memory.
For 1G hugepage, we can save 159M memory which is correspoinding to the
expected 160M memory.
