All of lore.kernel.org
 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, osalvador@suse.de,
	linux-mm@kvack.org
Subject: Re: [PATCH] mm: increase totalram_pages on freeing to buddy system
Date: Sun, 2 Jun 2024 00:58:21 +0000	[thread overview]
Message-ID: <20240602005820.2uk23ot4mskfl5sl@master> (raw)
In-Reply-To: <ac1a80a8-1a4f-47b6-8fc4-ce220ba76ead@redhat.com>

On Sat, Jun 01, 2024 at 06:15:33PM +0200, David Hildenbrand wrote:
>On 01.06.24 17:32, David Hildenbrand wrote:
>> On 01.06.24 15:34, Wei Yang wrote:
>> > Total memory represents pages managed by buddy system.
>> 
>> No, that's managed pages.
>> 
>> > After the
>> > introduction of DEFERRED_STRUCT_PAGE_INIT, it may count the pages before
>> > being managed.
>> > 
>> 
>> I recall one reason that is done, so other subsystem know the total
>> memory size even before deferred init is done.
>> 
>> > free_low_memory_core_early() returns number of pages for all free pages,
>> > even at this moment only early initialized pages are freed to buddy
>> > system. This means the total memory at this moment is not correct.
>> > 
>> > Let's increase it when pages are freed to buddy system.
>> 
>> I'm missing the "why", and the very first sentence of this patch is wrong.
>
>Correction: your statement was correct :) That's why
>adjust_managed_page_count() adjusts that as well.
>
>__free_pages_core() only adjusts managed page count, because it assumes
>totalram has already been adjusted early during boot.
>
>The reason we have this split for now, I think, is because of subsystems that
>call totalram_pages() during init.
>
>So the "why" question remains, because this change has the potential to break
>other stuff.
>

Thanks, I didn't notice this.

>-- 
>Cheers,
>
>David / dhildenb

-- 
Wei Yang
Help you, Help me


  parent reply	other threads:[~2024-06-02  0:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-01 13:34 [PATCH] mm: increase totalram_pages on freeing to buddy system Wei Yang
     [not found] ` <0316a276-a0d8-4fc2-ad67-0d4732b6d89b@redhat.com>
     [not found]   ` <ac1a80a8-1a4f-47b6-8fc4-ce220ba76ead@redhat.com>
2024-06-02  0:58     ` Wei Yang [this message]
2024-06-03  8:55       ` David Hildenbrand
2024-06-03 20:01         ` Wei Yang
2024-06-03 20:43           ` David Hildenbrand
2024-06-05 22:44             ` Wei Yang
2024-06-06  7:14               ` David Hildenbrand
2024-06-06 23:25                 ` Wei Yang
2024-06-07  1:50             ` Wei Yang
2024-06-11  8:48 ` kernel test robot

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=20240602005820.2uk23ot4mskfl5sl@master \
    --to=richard.weiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=osalvador@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.