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, brauner@kernel.org,
oleg@redhat.com, mjguzik@gmail.com, tandersen@netflix.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] mm/memblock: introduce a new helper memblock_estimated_nr_free_pages()
Date: Tue, 9 Jul 2024 00:56:18 +0000 [thread overview]
Message-ID: <20240709005618.a4uvufvnledd4vb5@master> (raw)
In-Reply-To: <e84fcec1-31bc-4397-851a-da70dd754b19@redhat.com>
On Mon, Jul 08, 2024 at 09:56:21AM +0200, David Hildenbrand wrote:
>On 08.07.24 03:00, Wei Yang wrote:
>> During bootup, system may need the number of free pages in the whole system
>> to do some calculation before all pages are freed to buddy system. Usually
>> this number is get from totalram_pages(). Since we plan to move the free
>> pages accounting in __free_pages_core(), this value may not represent
>> total free pages at the early stage, especially when
>> CONFIG_DEFERRED_STRUCT_PAGE_INIT is enabled.
>>
>> Instead of using raw memblock api, let's introduce a new helper for user
>> to get the estimated number of free pages from memblock point of view.
>>
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>> CC: David Hildenbrand <david@redhat.com>
>> Reviewed-by: David Hildenbrand <david@redhat.com>
>>
>> ---
>> v4: adjust comment per david's suggestion
>> ---
>> include/linux/memblock.h | 1 +
>> mm/memblock.c | 20 ++++++++++++++++++++
>> 2 files changed, 21 insertions(+)
>>
>> diff --git a/include/linux/memblock.h b/include/linux/memblock.h
>> index 40c62aca36ec..7d1c32b3dc12 100644
>> --- a/include/linux/memblock.h
>> +++ b/include/linux/memblock.h
>> @@ -486,6 +486,7 @@ static inline __init_memblock bool memblock_bottom_up(void)
>> phys_addr_t memblock_phys_mem_size(void);
>> phys_addr_t memblock_reserved_size(void);
>> +unsigned long memblock_estimated_nr_pages(void);
>
>^ stale name
My bad.
>
>> phys_addr_t memblock_start_of_DRAM(void);
>> phys_addr_t memblock_end_of_DRAM(void);
>> void memblock_enforce_memory_limit(phys_addr_t memory_limit);
>> diff --git a/mm/memblock.c b/mm/memblock.c
>> index e81fb68f7f88..26162902789f 100644
>> --- a/mm/memblock.c
>> +++ b/mm/memblock.c
>> @@ -1729,6 +1729,26 @@ phys_addr_t __init_memblock memblock_reserved_size(void)
>> return memblock.reserved.total_size;
>> }
>> +/**
>> + * memblock_estimated_nr_free_pages - return estimated number of free pages
>> + * from memblock point of view
>> + *
>> + * During bootup, subsystems might need a rough estimate of the number of free
>> + * pages in the whole system, before precise numbers are available from the
>> + * buddy. Especially with CONFIG_DEFERRED_STRUCT_PAGE_INIT, the numbers
>> + * obtained from the buddy might be very imprecise during bootup.
>> + *
>> + * While we can get the estimated number of free pages from memblock, which is
>> + * good enough for estimation.
>
>I'd drop that sentence.
>
Will update it.
>
>Apart form that LGTM
>
>--
>Cheers,
>
>David / dhildenb
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2024-07-09 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 1:00 Wei Yang
2024-07-08 1:00 ` [PATCH v4 2/3] kernel/fork.c: get totalram_pages from memblock to calculate max_threads Wei Yang
2024-07-08 7:56 ` David Hildenbrand
2024-07-08 1:00 ` [PATCH v4 3/3] kernel/fork.c: put set_max_threads()/task_struct_whitelist() in __init section Wei Yang
2024-07-08 7:56 ` [PATCH v4 1/3] mm/memblock: introduce a new helper memblock_estimated_nr_free_pages() David Hildenbrand
2024-07-09 0:56 ` 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=20240709005618.a4uvufvnledd4vb5@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjguzik@gmail.com \
--cc=oleg@redhat.com \
--cc=rppt@kernel.org \
--cc=tandersen@netflix.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