From: Muchun Song <muchun.song@linux.dev>
To: Usama Arif <usama.arif@bytedance.com>
Cc: linux-kernel@vger.kernel.org, fam.zheng@bytedance.com,
liangma@liangbit.com, simon.evans@bytedance.com,
punit.agrawal@bytedance.com, linux-mm@kvack.org,
mike.kravetz@oracle.com, rppt@kernel.org
Subject: Re: [v2 5/6] mm: move allocation of gigantic hstates to the start of mm_core_init
Date: Tue, 1 Aug 2023 11:07:59 +0800 [thread overview]
Message-ID: <e457b7b2-f268-3219-9639-9b09162aa4a9@linux.dev> (raw)
In-Reply-To: <20230730151606.2871391-6-usama.arif@bytedance.com>
On 2023/7/30 23:16, Usama Arif wrote:
> Whether the initialization of tail struct pages of a hugepage
> happens or not will become dependent on the commandline
> parameter hugetlb_free_vmemmap in the future. Hence,
> hugetlb_hstate_alloc_pages needs to be after command line parameters
> are parsed and the start of mm_core_init is a good point.
>
> Signed-off-by: Usama Arif <usama.arif@bytedance.com>
> ---
> mm/hugetlb.c | 18 ++++++++++--------
> mm/internal.h | 9 +++++++++
> mm/mm_init.c | 6 ++++++
> 3 files changed, 25 insertions(+), 8 deletions(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 541c07b6d60f..bf60545496d7 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -4400,14 +4400,6 @@ static int __init hugepages_setup(char *s)
> }
> }
>
> - /*
> - * Global state is always initialized later in hugetlb_init.
> - * But we need to allocate gigantic hstates here early to still
> - * use the bootmem allocator.
> - */
> - if (hugetlb_max_hstate && hstate_is_gigantic(parsed_hstate))
> - hugetlb_hstate_alloc_pages(parsed_hstate);
> -
> last_mhp = mhp;
>
> return 1;
> @@ -4419,6 +4411,16 @@ static int __init hugepages_setup(char *s)
> }
> __setup("hugepages=", hugepages_setup);
>
> +void __init hugetlb_hstate_alloc_gigantic_pages(void)
> +{
> + int i;
> +
> + for (i = 0; i < HUGE_MAX_HSTATE; i++) {
> + if (hstate_is_gigantic(&hstates[i]))
> + hugetlb_hstate_alloc_pages(&hstates[i]);
> + }
> +}
> +
> /*
> * hugepagesz command line processing
> * A specific huge page size can only be specified once with hugepagesz.
> diff --git a/mm/internal.h b/mm/internal.h
> index a7d9e980429a..692bb1136a39 100644
> --- a/mm/internal.h
> +++ b/mm/internal.h
> @@ -1102,4 +1102,13 @@ struct vma_prepare {
> struct vm_area_struct *remove;
> struct vm_area_struct *remove2;
> };
> +
> +#ifdef CONFIG_HUGETLBFS
> +void __init hugetlb_hstate_alloc_gigantic_pages(void);
> +#else
> +static inline void __init hugetlb_hstate_alloc_gigantic_pages(void);
> +{
> +}
> +#endif /* CONFIG_HUGETLBFS */
> +
> #endif /* __MM_INTERNAL_H */
> diff --git a/mm/mm_init.c b/mm/mm_init.c
> index a1963c3322af..f2751ccd7d99 100644
> --- a/mm/mm_init.c
> +++ b/mm/mm_init.c
> @@ -26,6 +26,7 @@
> #include <linux/pgtable.h>
> #include <linux/swap.h>
> #include <linux/cma.h>
> +#include <linux/hugetlb.h>
> #include "internal.h"
> #include "slab.h"
> #include "shuffle.h"
> @@ -2768,6 +2769,11 @@ static void __init mem_init_print_info(void)
> */
> void __init mm_core_init(void)
> {
> + /*
> + * We need to allocate gigantic hstates here early to still use the bootmem
> + * allocator. Non gigantic hstates are initialized later in hugetlb_init.
> + */
> + hugetlb_hstate_alloc_gigantic_pages();
Actually, I don't want to add hugetlb related information into a
common code. You just want to make hugetlb_hstate_alloc_gigantic_page()
happen after cmdline has been pased, maybe we could review this
cleanup [1], but it need some changes to satisfy your need. E.g. adding
"hugetlb_free_vmemmap" cmdline parsing in hugetlb_process_arg(). Then
we do not need to change mm/mm_init.c.
[1]
https://lore.kernel.org/linux-mm/20220616071827.3480-1-songmuchun@bytedance.com/
> /* Initializations relying on SMP setup */
> build_all_zonelists(NULL);
> page_alloc_init_cpuhp();
next prev parent reply other threads:[~2023-08-01 3:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 15:16 [v2 0/6] mm/memblock: Skip prep and initialization of struct pages freed later by HVO Usama Arif
2023-07-30 15:16 ` [v2 1/6] mm: hugetlb: Skip prep of tail pages when HVO is enabled Usama Arif
2023-07-31 23:18 ` Mike Kravetz
2023-08-02 10:05 ` [External] " Usama Arif
2023-08-01 2:04 ` Muchun Song
2023-08-02 10:06 ` [External] " Usama Arif
2023-07-30 15:16 ` [v2 2/6] mm: hugetlb_vmemmap: Use nid of the head page to reallocate it Usama Arif
2023-07-30 15:16 ` [v2 3/6] memblock: pass memblock_type to memblock_setclr_flag Usama Arif
2023-07-30 15:16 ` [v2 4/6] memblock: introduce MEMBLOCK_RSRV_NOINIT flag Usama Arif
2023-07-30 15:16 ` [v2 5/6] mm: move allocation of gigantic hstates to the start of mm_core_init Usama Arif
2023-07-30 16:49 ` kernel test robot
2023-08-01 3:07 ` Muchun Song [this message]
2023-07-30 15:16 ` [v2 6/6] mm: hugetlb: Skip initialization of struct pages freed later by HVO Usama Arif
2023-07-30 19:33 ` kernel test robot
2023-07-31 0:11 ` kernel test robot
2023-07-31 6:46 ` kernel test robot
2023-07-30 22:28 ` [v2 0/6] mm/memblock: Skip prep and " Usama Arif
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=e457b7b2-f268-3219-9639-9b09162aa4a9@linux.dev \
--to=muchun.song@linux.dev \
--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=punit.agrawal@bytedance.com \
--cc=rppt@kernel.org \
--cc=simon.evans@bytedance.com \
--cc=usama.arif@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;
as well as URLs for NNTP newsgroup(s).