From: Usama Arif <usama.arif@bytedance.com>
To: linux-mm@kvack.org, muchun.song@linux.dev,
mike.kravetz@oracle.com, rppt@kernel.org
Cc: linux-kernel@vger.kernel.org, fam.zheng@bytedance.com,
liangma@liangbit.com, simon.evans@bytedance.com,
punit.agrawal@bytedance.com
Subject: Re: [RFC 0/4] mm/memblock: Skip prep and initialization of struct pages freed later by HVO
Date: Wed, 26 Jul 2023 11:34:14 +0100 [thread overview]
Message-ID: <03476b1d-c825-0ab6-73bc-b98419d3dff6@bytedance.com> (raw)
In-Reply-To: <20230724134644.1299963-1-usama.arif@bytedance.com>
On 24/07/2023 14:46, Usama Arif wrote:
> If the region is for gigantic hugepages and if HVO is enabled, then those
> struct pages which will be freed later by HVO don't need to be prepared and
> initialized. This can save significant time when a large number of hugepages
> are allocated at boot time.
>
> For a 1G hugepage, this series avoid initialization and preparation of
> 262144 - 64 = 262080 struct pages per hugepage.
>
> When tested on a 512G system (which can allocate max 500 1G hugepages), the
> kexec-boot time with HVO and DEFERRED_STRUCT_PAGE_INIT enabled without this
> patchseries to running init is 3.9 seconds. With this patch it is 1.2 seconds.
> This represents an approximately 70% reduction in boot time and will
> significantly reduce server downtime when using a large number of
> gigantic pages.
There were a few errors reported by kernel-bot if different config
options were changed (CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP disabled,
CONFIG_CMA enabled). I will fix these in the next revision if the
general approach in the patches looks good to the community to start review.
Thanks,
Usama
>
> Thanks,
> Usama
>
> Usama Arif (4):
> mm/hugetlb: Skip prep of tail pages when HVO is enabled
> mm/memblock: Add hugepage_size member to struct memblock_region
> mm/hugetlb_vmemmap: Use nid of the head page to reallocate it
> mm/memblock: Skip initialization of struct pages freed later by HVO
>
> arch/arm64/mm/kasan_init.c | 2 +-
> arch/powerpc/platforms/pasemi/iommu.c | 2 +-
> arch/powerpc/platforms/pseries/setup.c | 4 +-
> arch/powerpc/sysdev/dart_iommu.c | 2 +-
> include/linux/memblock.h | 8 +-
> mm/cma.c | 4 +-
> mm/hugetlb.c | 36 +++++---
> mm/hugetlb_vmemmap.c | 6 +-
> mm/hugetlb_vmemmap.h | 4 +
> mm/memblock.c | 87 +++++++++++++-------
> mm/mm_init.c | 2 +-
> mm/sparse-vmemmap.c | 2 +-
> tools/testing/memblock/tests/alloc_nid_api.c | 2 +-
> 13 files changed, 106 insertions(+), 55 deletions(-)
>
prev parent reply other threads:[~2023-07-26 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 13:46 Usama Arif
2023-07-24 13:46 ` [RFC 1/4] mm/hugetlb: Skip prep of tail pages when HVO is enabled Usama Arif
2023-07-24 13:46 ` [RFC 2/4] mm/memblock: Add hugepage_size member to struct memblock_region Usama Arif
2023-07-26 11:01 ` Mike Rapoport
2023-07-26 15:02 ` [External] " Usama Arif
2023-07-27 4:30 ` Mike Rapoport
2023-07-27 20:56 ` Usama Arif
2023-07-24 13:46 ` [RFC 3/4] mm/hugetlb_vmemmap: Use nid of the head page to reallocate it Usama Arif
2023-07-24 13:46 ` [RFC 4/4] mm/memblock: Skip initialization of struct pages freed later by HVO Usama Arif
2023-07-26 10:34 ` Usama Arif [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03476b1d-c825-0ab6-73bc-b98419d3dff6@bytedance.com \
--to=usama.arif@bytedance.com \
--cc=fam.zheng@bytedance.com \
--cc=liangma@liangbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=punit.agrawal@bytedance.com \
--cc=rppt@kernel.org \
--cc=simon.evans@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox