linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
	rppt@kernel.org, akpm@linux-foundation.org, 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 23:58:05 +0000	[thread overview]
Message-ID: <20240611235805.zmkamtexok572vq5@master> (raw)
In-Reply-To: <6329e2bc-a903-43a2-a676-3e83ec2b1071@redhat.com>

On Tue, Jun 11, 2024 at 05:12:13PM +0200, David Hildenbrand wrote:
>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

-- 
Wei Yang
Help you, Help me


      reply	other threads:[~2024-06-11 23:58 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
2024-06-11 23:58   ` Wei Yang [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=20240611235805.zmkamtexok572vq5@master \
    --to=richard.weiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --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