linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@redhat.com>,
	Oscar Salvador <osalvador@suse.de>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Naoya Horiguchi <nao.horiguchi@gmail.com>, <linux-mm@kvack.org>
Subject: Re: [PATCH v2 1/5] mm: memory_hotplug: remove head variable in do_migrate_range()
Date: Mon, 19 Aug 2024 18:41:56 +0800	[thread overview]
Message-ID: <23c1c683-241a-4121-89d6-3e317b0ee0f3@huawei.com> (raw)
In-Reply-To: <20240819102818.0000080b@Huawei.com>



On 2024/8/19 17:28, Jonathan Cameron wrote:
> On Sat, 17 Aug 2024 16:49:37 +0800
> Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
> 
>> Directly use a folio for HugeTLB and THP when calculate the next pfn,
>> then remove unused head variable.
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> 
> Hi,
> 
> I was curious so had a read and have a quick comment
> on the comment.
> 
> 
>> ---
>>   mm/memory_hotplug.c | 22 ++++++++++++++--------
>>   1 file changed, 14 insertions(+), 8 deletions(-)
>>
>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>> index df291f2e509d..dc19b0e28fbc 100644
>> --- a/mm/memory_hotplug.c
>> +++ b/mm/memory_hotplug.c
>> @@ -1773,7 +1773,7 @@ static int scan_movable_pages(unsigned long start, unsigned long end,
>>   static void do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
>>   {
>>   	unsigned long pfn;
>> -	struct page *page, *head;
>> +	struct page *page;
>>   	LIST_HEAD(source);
>>   	static DEFINE_RATELIMIT_STATE(migrate_rs, DEFAULT_RATELIMIT_INTERVAL,
>>   				      DEFAULT_RATELIMIT_BURST);
>> @@ -1786,14 +1786,20 @@ static void do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
>>   			continue;
>>   		page = pfn_to_page(pfn);
>>   		folio = page_folio(page);
>> -		head = &folio->page;
>>   
>> -		if (PageHuge(page)) {
>> -			pfn = page_to_pfn(head) + compound_nr(head) - 1;
>> -			isolate_hugetlb(folio, &source);
>> -			continue;
>> -		} else if (PageTransHuge(page))
>> -			pfn = page_to_pfn(head) + thp_nr_pages(page) - 1;
>> +		/*
>> +		 * The folio hold no reference or lock, it might be changed
>> +		 * concurrently(eg, split), folio_nr_pages() may read garbage,
>> +		 * but out loop could handle that as it revisits the split
>> +		 * folio later.
>> +		 */
> Perhaps reword this (it confused me a bit) I'm not sure I've retained
> the intended meaning!
> 
> 		* No reference or lock is held on the folio, so it might
> 		* be modified concurrently (e.g. split).  As such,
> 		* folio_nr_pages() may read garbage.  This is fine as the
> 		* outer loop will revisit the split folio later.

Thanks. hope Andrew could squash it if no more comments about this
patchset, or I will resend a new version with comment changes.


> 
> 
>> +		if (folio_test_large(folio)) {
>> +			pfn = folio_pfn(folio) + folio_nr_pages(folio) - 1;
>> +			if (folio_test_hugetlb(folio)) {
>> +				isolate_hugetlb(folio, &source);
>> +				continue;
>> +			}
>> +		}
>>   
>>   		/*
>>   		 * HWPoison pages have elevated reference counts so the migration would
> 


  reply	other threads:[~2024-08-19 10:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17  8:49 [PATCH resend v2 0/5] mm: memory_hotplug: improve do_migrate_range() Kefeng Wang
2024-08-17  8:49 ` [PATCH v2 1/5] mm: memory_hotplug: remove head variable in do_migrate_range() Kefeng Wang
2024-08-19  9:28   ` Jonathan Cameron
2024-08-19 10:41     ` Kefeng Wang [this message]
2024-08-21  7:33     ` Miaohe Lin
2024-08-26 14:42   ` David Hildenbrand
2024-08-17  8:49 ` [PATCH v2 2/5] mm: memory-failure: add unmap_posioned_folio() Kefeng Wang
2024-08-21  7:40   ` Miaohe Lin
2024-08-21  8:54     ` Kefeng Wang
2024-08-17  8:49 ` [PATCH v2 3/5] mm: memory_hotplug: check hwpoisoned page firstly in do_migrate_range() Kefeng Wang
2024-08-22  6:52   ` Miaohe Lin
2024-08-22 11:35     ` Kefeng Wang
2024-08-26 14:46   ` David Hildenbrand
2024-08-27  1:13     ` Kefeng Wang
2024-08-27  2:12       ` Miaohe Lin
2024-08-27 15:11         ` David Hildenbrand
2024-08-17  8:49 ` [PATCH v2 4/5] mm: migrate: add isolate_folio_to_list() Kefeng Wang
2024-08-20  9:32   ` Miaohe Lin
2024-08-20  9:46     ` Kefeng Wang
2024-08-21  2:00       ` Miaohe Lin
2024-08-21  2:14         ` Kefeng Wang
2024-08-22  6:56           ` Miaohe Lin
2024-08-26 14:50   ` David Hildenbrand
2024-08-27  1:19     ` Kefeng Wang
2024-08-17  8:49 ` [PATCH v2 5/5] mm: memory_hotplug: unify Huge/LRU/non-LRU movable folio isolation Kefeng Wang
2024-08-22  7:20   ` Miaohe Lin
2024-08-22 12:08     ` Kefeng Wang
2024-08-26 14:55   ` David Hildenbrand
2024-08-27  1:26     ` Kefeng Wang
2024-08-27 15:10       ` David Hildenbrand
2024-08-27 15:35         ` Kefeng Wang
2024-08-27 15:38           ` David Hildenbrand
  -- strict thread matches above, loose matches on Subject: below --
2024-08-16  9:04 [PATCH v2 0/5] mm: memory_hotplug: improve do_migrate_range() Kefeng Wang
2024-08-16  9:04 ` [PATCH v2 1/5] mm: memory_hotplug: remove head variable in do_migrate_range() Kefeng 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=23c1c683-241a-4121-89d6-3e317b0ee0f3@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    /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