linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	<akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/huge_memory: remove unneeded local variable follflags
Date: Fri, 11 Mar 2022 15:01:27 +0800	[thread overview]
Message-ID: <84c5befc-02b0-99cd-a670-8ed0b08dd820@huawei.com> (raw)
In-Reply-To: <2abaff3b-455a-c345-be93-0036b8dd1519@arm.com>

On 2022/3/11 14:39, Anshuman Khandual wrote:
> 
> 
> On 3/11/22 11:56, Miaohe Lin wrote:
>> On 2022/3/11 12:51, Anshuman Khandual wrote:
>>> Hi Miaohe,
>>>
>>> On 3/10/22 18:42, Miaohe Lin wrote:
>>>> We can pass FOLL_GET | FOLL_DUMP to follow_page directly to simplify
>>>> the code a bit.
>>>>
>>>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>>>> ---
>>>>  mm/huge_memory.c | 4 +---
>>>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>>>
>>>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>>>> index 3557aabe86fe..418d077da246 100644
>>>> --- a/mm/huge_memory.c
>>>> +++ b/mm/huge_memory.c
>>>> @@ -2838,7 +2838,6 @@ static int split_huge_pages_pid(int pid, unsigned long vaddr_start,
>>>>  	 */
>>>>  	for (addr = vaddr_start; addr < vaddr_end; addr += PAGE_SIZE) {
>>>>  		struct vm_area_struct *vma = find_vma(mm, addr);
>>>> -		unsigned int follflags;
>>>>  		struct page *page;
>>>>  
>>>>  		if (!vma || addr < vma->vm_start)
>>>> @@ -2851,8 +2850,7 @@ static int split_huge_pages_pid(int pid, unsigned long vaddr_start,
>>>>  		}
>>>>  
>>>>  		/* FOLL_DUMP to ignore special (like zero) pages */
>>>> -		follflags = FOLL_GET | FOLL_DUMP;
>>>> -		page = follow_page(vma, addr, follflags);
>>>> +		page = follow_page(vma, addr, FOLL_GET | FOLL_DUMP);
>>>>  
>>>>  		if (IS_ERR(page))
>>>>  			continue;
>>>
>>> LGTM, but there is another similar instance in add_page_for_migration()
>>> inside mm/migrate.c, requiring this exact clean up.
>>>
>>
>> Thanks for comment. That similar case is done in my previous patch series[1]
>> aimed at migration cleanup and fixup. It might be more suitable to do that
>> clean up in that specialized series?
> 
> Both these similar scenarios i.e the one proposed here and other one in the
> migration series, should be folded into a separate single patch, either here
> or in the series itself.

Looks fine to me. Will do. Thanks.

> 
>>
>> [1]:https://lore.kernel.org/linux-mm/20220304093409.25829-4-linmiaohe@huawei.com/
>>
>>> Hence with that change in place.
>>>
>>> Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
>>
>> Thanks again.
>>
>>> .
>>>
>>
> .
> 



  reply	other threads:[~2022-03-11  7:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 13:12 Miaohe Lin
2022-03-11  4:51 ` Anshuman Khandual
2022-03-11  6:26   ` Miaohe Lin
2022-03-11  6:39     ` Anshuman Khandual
2022-03-11  7:01       ` Miaohe Lin [this message]
2022-03-11  9:56 ` David Hildenbrand

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=84c5befc-02b0-99cd-a670-8ed0b08dd820@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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