From: Mike Rapoport <rppt@kernel.org>
To: Baoquan He <bhe@redhat.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, mgorman@suse.de
Subject: Re: [PATCH 1/7] mm: move array mem_section init code out of memory_present()
Date: Tue, 2 Apr 2024 11:19:26 +0300 [thread overview]
Message-ID: <Zgu_jjcLtEF-TlUj@kernel.org> (raw)
In-Reply-To: <20240326061134.1055295-2-bhe@redhat.com>
On Tue, Mar 26, 2024 at 02:11:27PM +0800, Baoquan He wrote:
> When CONFIG_SPARSEMEM_EXTREME is enabled, mem_section need be initialized
> to point at a two-dimensional array, and its 1st dimension of length
> NR_SECTION_ROOTS will be dynamically allocated. Once the allocation is
> done, it's available for all nodes.
>
> So take the 1st dimension of mem_section initialization out of
> memory_present()(), and put it into memblocks_present() which is a more
> appripriate place.
>
> Signed-off-by: Baoquan He <bhe@redhat.com>
> ---
> mm/sparse.c | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/mm/sparse.c b/mm/sparse.c
> index aed0951b87fa..46e88549d1a6 100644
> --- a/mm/sparse.c
> +++ b/mm/sparse.c
> @@ -226,19 +226,6 @@ static void __init memory_present(int nid, unsigned long start, unsigned long en
> {
> unsigned long pfn;
>
> -#ifdef CONFIG_SPARSEMEM_EXTREME
> - if (unlikely(!mem_section)) {
> - unsigned long size, align;
> -
> - size = sizeof(struct mem_section *) * NR_SECTION_ROOTS;
> - align = 1 << (INTERNODE_CACHE_SHIFT);
> - mem_section = memblock_alloc(size, align);
> - if (!mem_section)
> - panic("%s: Failed to allocate %lu bytes align=0x%lx\n",
> - __func__, size, align);
> - }
> -#endif
> -
> start &= PAGE_SECTION_MASK;
> mminit_validate_memmodel_limits(&start, &end);
> for (pfn = start; pfn < end; pfn += PAGES_PER_SECTION) {
> @@ -267,6 +254,19 @@ static void __init memblocks_present(void)
> unsigned long start, end;
> int i, nid;
>
> +#ifdef CONFIG_SPARSEMEM_EXTREME
> + if (unlikely(!mem_section)) {
With the new calling sequence sparse_init() -> memblocks_present() ->
allocate mem_section, mem_section here will be NULL, so this if is not
really relevant. We might want to add WARN_ON_ONCE(mem_section) just in
case to catch multiple calls to sparse_init().
> + unsigned long size, align;
> +
> + size = sizeof(struct mem_section *) * NR_SECTION_ROOTS;
> + align = 1 << (INTERNODE_CACHE_SHIFT);
> + mem_section = memblock_alloc(size, align);
> + if (!mem_section)
> + panic("%s: Failed to allocate %lu bytes align=0x%lx\n",
> + __func__, size, align);
> + }
> +#endif
> +
> for_each_mem_pfn_range(i, MAX_NUMNODES, &start, &end, &nid)
> memory_present(nid, start, end);
> }
> --
> 2.41.0
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2024-04-02 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 6:11 [PATCH 0/7] mm/init: minor clean up and improvement Baoquan He
2024-03-26 6:11 ` [PATCH 1/7] mm: move array mem_section init code out of memory_present() Baoquan He
2024-04-02 8:19 ` Mike Rapoport [this message]
2024-04-04 1:38 ` Baoquan He
2024-03-26 6:11 ` [PATCH 2/7] mm/init: remove the unnecessary special treatment for memory-less node Baoquan He
2024-04-02 8:32 ` Mike Rapoport
2024-04-04 3:23 ` Baoquan He
2024-04-09 15:40 ` Mike Rapoport
2024-04-10 3:38 ` Baoquan He
2024-04-10 3:35 ` [PATCH v2 " Baoquan He
2024-03-26 6:11 ` [PATCH 3/7] mm: make __absent_pages_in_range() as static Baoquan He
2024-04-02 8:29 ` Mike Rapoport
2024-03-26 6:11 ` [PATCH 4/7] mm/page_alloc.c: remove unneeded codes in !NUMA version of build_zonelists() Baoquan He
2024-03-27 12:06 ` [PATCH v2 " Baoquan He
2024-03-26 6:11 ` [PATCH 5/7] mm/mm_init.c: remove the outdated code comment above deferred_grow_zone() Baoquan He
2024-04-02 8:30 ` Mike Rapoport
2024-03-26 6:11 ` [PATCH 6/7] mm/page_alloc.c: don't show protection in zone's ->lowmem_reserve[] for empty zone Baoquan He
2024-03-26 6:11 ` [PATCH 7/7] mm/page_alloc.c: change the array-length to MIGRATE_PCPTYPES Baoquan He
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=Zgu_jjcLtEF-TlUj@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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