From: "Huang, Ying" <ying.huang@intel.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: <akpm@linux-foundation.org>, <mgorman@techsingularity.net>,
<vbabka@suse.cz>, <mhocko@suse.com>, <david@redhat.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mm/page_alloc: drop the unnecessary pfn_valid() for start pfn
Date: Sun, 23 Apr 2023 08:55:45 +0800 [thread overview]
Message-ID: <87h6t7s9gu.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <c2eee65ecd15779721af85c9ff109a35345b52d4.1682158312.git.baolin.wang@linux.alibaba.com> (Baolin Wang's message of "Sat, 22 Apr 2023 18:15:17 +0800")
Baolin Wang <baolin.wang@linux.alibaba.com> writes:
> We've already used pfn_to_online_page() for start pfn to make sure
> it is online and valid, so the pfn_valid() for the start pfn is
> unnecessary, drop it.
>
> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
Thanks!
Reviewed-by: "Huang, Ying" <ying.huang@intel.com>
> ---
> mm/page_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 9de2a18519a1..6457b64fe562 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -1512,7 +1512,7 @@ struct page *__pageblock_pfn_to_page(unsigned long start_pfn,
> /* end_pfn is one past the range we are checking */
> end_pfn--;
>
> - if (!pfn_valid(start_pfn) || !pfn_valid(end_pfn))
> + if (!pfn_valid(end_pfn))
> return NULL;
>
> start_page = pfn_to_online_page(start_pfn);
prev parent reply other threads:[~2023-04-23 0:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 10:15 Baolin Wang
2023-04-22 10:15 ` [PATCH 2/2] mm/page_alloc: add some comments to explain the possible hole in __pageblock_pfn_to_page() Baolin Wang
2023-04-23 1:13 ` Huang, Ying
2023-04-23 1:27 ` Baolin Wang
2023-04-23 5:19 ` Mike Rapoport
2023-04-23 6:00 ` Baolin Wang
2023-04-22 20:37 ` [PATCH 1/2] mm/page_alloc: drop the unnecessary pfn_valid() for start pfn David Hildenbrand
2023-04-23 0:55 ` Huang, Ying [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=87h6t7s9gu.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
/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