linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Michal Hocko <mhocko@suse.com>
Cc: akpm@linux-foundation.org, rppt@kernel.org, ying.huang@intel.com,
	mgorman@techsingularity.net, vbabka@suse.cz, david@redhat.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mm/page_alloc: drop the unnecessary pfn_valid() for start pfn
Date: Mon, 24 Apr 2023 18:46:40 +0800	[thread overview]
Message-ID: <7525a9f6-b431-4404-2878-898e52905d4a@linux.alibaba.com> (raw)
In-Reply-To: <ZEZQ9EpUY8Mj5TwQ@dhcp22.suse.cz>



On 4/24/2023 5:50 PM, Michal Hocko wrote:
> On Sun 23-04-23 18:59:10, Baolin Wang wrote:
>> We've already used pfn_to_online_page() for start pfn to make sure
> 
> Who is we? I do not see any note explicitly requiring that start_pfn has
> to be valid for __pageblock_pfn_to_page.

Sorry for confusing, what I mean is the __pageblock_pfn_to_page() 
function, which has used pfn_to_online_page() for start pfn. So the 
pfn_valid() in __pageblock_pfn_to_page() for start pfn is unnecessary.

I will update the commit log to make it clear.

>> 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>
>> Reviewed-by: David Hildenbrand <david@redhat.com>
>> Reviewed-by: "Huang, Ying" <ying.huang@intel.com>
>> ---
>> Changes from v1:
>>   - Collect reviewed tags. Thanks David and Ying.
>> ---
>>   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);
>> -- 
>> 2.27.0
> 


  reply	other threads:[~2023-04-24 10:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 10:59 Baolin Wang
2023-04-23 10:59 ` [PATCH v2 2/2] mm/page_alloc: add some comments to explain the possible hole in __pageblock_pfn_to_page() Baolin Wang
2023-04-24  2:24   ` Huang, Ying
2023-04-24  9:54   ` Michal Hocko
2023-04-24 11:20     ` Baolin Wang
2023-04-24 11:34       ` Michal Hocko
2023-04-24 11:40         ` Baolin Wang
2023-04-24 12:08           ` Michal Hocko
2023-04-24 12:48             ` Baolin Wang
2023-04-24 13:08               ` Michal Hocko
2023-04-24  9:50 ` [PATCH v2 1/2] mm/page_alloc: drop the unnecessary pfn_valid() for start pfn Michal Hocko
2023-04-24 10:46   ` Baolin Wang [this message]
2023-04-24 10:54     ` Michal Hocko
2023-04-24 11:21       ` Baolin Wang

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=7525a9f6-b431-4404-2878-898e52905d4a@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=ying.huang@intel.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