linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Wei Yang <richard.weiyang@gmail.com>,
	rppt@kernel.org, akpm@linux-foundation.org
Cc: linux-mm@kvack.org
Subject: Re: [PATCH v2] mm/mm_init.c: print mem_init info after defer_init is done
Date: Tue, 11 Jun 2024 17:12:13 +0200	[thread overview]
Message-ID: <6329e2bc-a903-43a2-a676-3e83ec2b1071@redhat.com> (raw)
In-Reply-To: <20240611145223.16872-1-richard.weiyang@gmail.com>

On 11.06.24 16:52, Wei Yang wrote:
> Current call flow looks like this:
> 
> start_kernel
>    mm_core_init
>      mem_init
>      mem_init_print_info
>    rest_init
>      kernel_init
>        kernel_init_freeable
>          page_alloc_init_late
>            deferred_init_memmap
> 
> If CONFIG_DEFERRED_STRUCT_PAGE_INIT, the time mem_init_print_info()
> calls, pages are not totally initialized and freed to buddy.
> 
> This has one issue
> 
>    * nr_free_pages() just contains partial free pages in the system,
>      which is not we expect.
> 
> Let's print the mem info after defer_init is done.
> 
> Also this would help changing totalram_pages accounting, since we plan
> to move the accounting into __free_pages_core().
> 
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> CC: David Hildenbrand <david@redhat.com>

Acked-by: David Hildenbrand <david@redhat.com>

Hoping this won't reveal other surprises.

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-06-11 15:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 14:52 Wei Yang
2024-06-11 15:12 ` David Hildenbrand [this message]
2024-06-11 23:58   ` Wei Yang

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=6329e2bc-a903-43a2-a676-3e83ec2b1071@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=richard.weiyang@gmail.com \
    --cc=rppt@kernel.org \
    /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