From: Wei Yang <richard.weiyang@gmail.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: richard@nod.at, anton.ivanov@cambridgegreys.com,
johannes@sipsolutions.net, linux-um@lists.infradead.org,
linux-mm@kvack.org, Jeff Dike <jdike@linux.intel.com>,
Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>,
Alasdair G Kergon <agk@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v2] um/mm: remove redundant assignment of max_low_pfn
Date: Tue, 23 Jul 2024 03:43:04 +0000 [thread overview]
Message-ID: <20240723034304.4kbzxsaapxanxms4@master> (raw)
In-Reply-To: <20240615034150.2958-1-richard.weiyang@gmail.com>
Would someone pick up this one?
On Sat, Jun 15, 2024 at 03:41:50AM +0000, Wei Yang wrote:
>Current calculation of max_low_pfn is introduced in commit af84eab20891
>("[PATCH] uml: fix LVM crash"). It is intended to set max_low_pfn to the
>same value as max_pfn.
>
>But I am not sure why the max_pfn is set to totalram_pages, which
>represents the number of usable pages in system instead of an absolute
>page frame number. (The change history stops there.)
>
>While we have already calculate it in setup_physmem(), so not necessary
>to do it again.
>
>Also this would help changing totalram_pages accounting, since we plan
>to move the accounting into __free_pages_core(). With this change,
>totalram_pages may not represent the total usable pages at this point,
>since some pages would be deferred initialized.
>
>Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>CC: Jeff Dike <jdike@linux.intel.com>
>Cc: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
>Cc: Alasdair G Kergon <agk@redhat.com>
>CC: Andrew Morton <akpm@linux-foundation.org>
>CC: Mike Rapoport (IBM) <rppt@kernel.org>
>CC: David Hildenbrand <david@redhat.com>
>
>---
>v2: remove redundant assignment of max_low_pfn
>---
> arch/um/kernel/mem.c | 1 -
> 1 file changed, 1 deletion(-)
>
>diff --git a/arch/um/kernel/mem.c b/arch/um/kernel/mem.c
>index ca91accd64fc..a5b4fe2ad931 100644
>--- a/arch/um/kernel/mem.c
>+++ b/arch/um/kernel/mem.c
>@@ -73,7 +73,6 @@ void __init mem_init(void)
>
> /* this will put all low memory onto the freelists */
> memblock_free_all();
>- max_low_pfn = totalram_pages();
> max_pfn = max_low_pfn;
> kmalloc_ok = 1;
> }
>--
>2.34.1
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2024-07-23 3:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 3:41 Wei Yang
2024-06-15 8:17 ` Mike Rapoport
2024-07-23 3:43 ` 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=20240723034304.4kbzxsaapxanxms4@master \
--to=richard.weiyang@gmail.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=blaisorblade@yahoo.it \
--cc=david@redhat.com \
--cc=jdike@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-mm@kvack.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--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