From: Wei Yang <richard.weiyang@gmail.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
gerald.schaefer@linux.ibm.com, hca@linux.ibm.com,
rppt@kernel.org, akpm@linux-foundation.org, brauner@kernel.org,
oleg@redhat.com, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v6 1/3] mm/memblock: introduce a new helper memblock_estimated_nr_free_pages()
Date: Thu, 8 Aug 2024 14:24:05 +0000 [thread overview]
Message-ID: <20240808142405.ttlcfkximywtde6i@master> (raw)
In-Reply-To: <ZrSYruB/Aa8+oBoZ@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com>
On Thu, Aug 08, 2024 at 12:06:38PM +0200, Alexander Gordeev wrote:
>On Thu, Aug 08, 2024 at 12:14:13AM +0000, Wei Yang wrote:
>
>Hi Wei,
>
>...
>> + * Return:
>> + * An estimated number of free pages from memblock point of view.
>> + */
>> +unsigned long __init memblock_estimated_nr_free_pages(void)
>> +{
>> + return PHYS_PFN(memblock_phys_mem_size() - memblock_reserved_size());
>> +}
>
>This could possibly be short on up to two pages due to lack of alignment.
>The current uses are okay, but since you make it generic it probably matters.
>
I don't follow, would you mind giving more detail?
>Also, the returned value is not an estimation. Meaning the function name
>is rather unfortunate AFAICT.
From my point of view, this is an estimation for two reasons:
* value from memblock_xxx is not page size aligned
* reserved memory maybe released during boot stage
It is not that easy to get the exact number of free pages here. Do I miss
something?
>
>> +#define PHYS_PFN(x) ((unsigned long)((x) >> PAGE_SHIFT))
>
>Thanks!
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2024-08-08 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 0:14 [PATCH v6 1/3] mm/memblock: introduce a new helper memblock_estimated_nr_free_pages() Wei Yang
2024-08-08 0:14 ` [PATCH v6 2/3] kernel/fork.c: get estimated free pages by memblock api Wei Yang
2024-08-08 8:54 ` David Hildenbrand
2024-08-08 0:14 ` [PATCH v6 3/3] s390/mm: " Wei Yang
2024-08-08 8:54 ` David Hildenbrand
2024-08-08 10:06 ` [PATCH v6 1/3] mm/memblock: introduce a new helper memblock_estimated_nr_free_pages() Alexander Gordeev
2024-08-08 14:24 ` Wei Yang [this message]
2024-08-08 16:10 ` Alexander Gordeev
2024-08-11 16:38 ` Mike Rapoport
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=20240808142405.ttlcfkximywtde6i@master \
--to=richard.weiyang@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=oleg@redhat.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