All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: akpm@linux-foundation.org, mgorman@techsingularity.net,
	vbabka@suse.cz, david@redhat.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mm: compaction: skip the memory hole rapidly when isolating free pages
Date: Mon, 10 Jul 2023 17:26:51 +0800	[thread overview]
Message-ID: <36747b09-8141-019f-85dd-59f3d4623ec1@linux.alibaba.com> (raw)
In-Reply-To: <87pm50fg88.fsf@yhuang6-desk2.ccr.corp.intel.com>



On 7/10/2023 2:11 PM, Huang, Ying wrote:
> Baolin Wang <baolin.wang@linux.alibaba.com> writes:
> 
>> On my machine with below memory layout, and I can see it will take more
>> time to skip the larger memory hole (range: 0x100000000 - 0x1800000000)
>> when isolating free pages. So adding a new helper to skip the memory
>> hole rapidly, which can reduce the time consumed from about 70us to less
>> than 1us.
>>
>> [    0.000000] Zone ranges:
>> [    0.000000]   DMA      [mem 0x0000000040000000-0x00000000ffffffff]
>> [    0.000000]   DMA32    empty
>> [    0.000000]   Normal   [mem 0x0000000100000000-0x0000001fa7ffffff]
> 
> The memory hole is at the beginning of zone NORMAL?  If so, should zone

No, the memory hole range is 0x1000000000 - 0x1800000000, and the normal 
zone is start from 0x100000000.

I'm sorry I made a typo in the commit message, which confuses you. The 
memory hole range should be: 0x1000000000 - 0x1800000000. I updated the 
commit message to the following and addressed David's comment:

"
Just like commit 9721fd82351d ("mm: compaction: skip memory hole rapidly
when isolating migratable pages"), I can see it will also take more
time to skip the larger memory hole (range: 0x1000000000 - 0x1800000000)
when isolating free pages on my machine with below memory layout. So 
like commit 9721fd82351d, adding a new helper to skip the memory hole 
rapidly, which can reduce the time consumed from about 70us to less than 
1us.

[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000040000000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   [mem 0x0000000100000000-0x0000001fa7ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x0000000fffffffff]
[    0.000000]   node   0: [mem 0x0000001800000000-0x0000001fa3c7ffff]
[    0.000000]   node   0: [mem 0x0000001fa3c80000-0x0000001fa3ffffff]
[    0.000000]   node   0: [mem 0x0000001fa4000000-0x0000001fa402ffff]
[    0.000000]   node   0: [mem 0x0000001fa4030000-0x0000001fa40effff]
[    0.000000]   node   0: [mem 0x0000001fa40f0000-0x0000001fa73cffff]
[    0.000000]   node   0: [mem 0x0000001fa73d0000-0x0000001fa745ffff]
[    0.000000]   node   0: [mem 0x0000001fa7460000-0x0000001fa746ffff]
[    0.000000]   node   0: [mem 0x0000001fa7470000-0x0000001fa758ffff]
[    0.000000]   node   0: [mem 0x0000001fa7590000-0x0000001fa7ffffff]
"

> NORMAL start at 0x1800000000?  And, the free pages will not be scanned
> there?  Or my understanding were wrong. >
>> [    0.000000] Movable zone start for each node
>> [    0.000000] Early memory node ranges
>> [    0.000000]   node   0: [mem 0x0000000040000000-0x0000000fffffffff]
>> [    0.000000]   node   0: [mem 0x0000001800000000-0x0000001fa3c7ffff]
>> [    0.000000]   node   0: [mem 0x0000001fa3c80000-0x0000001fa3ffffff]
>> [    0.000000]   node   0: [mem 0x0000001fa4000000-0x0000001fa402ffff]
>> [    0.000000]   node   0: [mem 0x0000001fa4030000-0x0000001fa40effff]
>> [    0.000000]   node   0: [mem 0x0000001fa40f0000-0x0000001fa73cffff]
>> [    0.000000]   node   0: [mem 0x0000001fa73d0000-0x0000001fa745ffff]
>> [    0.000000]   node   0: [mem 0x0000001fa7460000-0x0000001fa746ffff]
>> [    0.000000]   node   0: [mem 0x0000001fa7470000-0x0000001fa758ffff]
>> [    0.000000]   node   0: [mem 0x0000001fa7590000-0x0000001fa7ffffff]
>>
>> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
>> ---
>>   mm/compaction.c | 30 +++++++++++++++++++++++++++++-
>>   1 file changed, 29 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/compaction.c b/mm/compaction.c
>> index 43358efdbdc2..9641e2131901 100644
>> --- a/mm/compaction.c
>> +++ b/mm/compaction.c
>> @@ -249,11 +249,31 @@ static unsigned long skip_offline_sections(unsigned long start_pfn)
>>   
>>   	return 0;
>>   }
>> +
>> +static unsigned long skip_offline_sections_reverse(unsigned long start_pfn)
>> +{
>> +	unsigned long start_nr = pfn_to_section_nr(start_pfn);
>> +
>> +	if (!start_nr || online_section_nr(start_nr))
>> +		return 0;
>> +
>> +	while (start_nr-- > 0) {
>> +		if (online_section_nr(start_nr))
>> +			return section_nr_to_pfn(start_nr) + PAGES_PER_SECTION - 1;
>> +	}
>> +
>> +	return 0;
>> +}
>>   #else
>>   static unsigned long skip_offline_sections(unsigned long start_pfn)
>>   {
>>   	return 0;
>>   }
>> +
>> +static unsigned long skip_offline_sections_reverse(unsigned long start_pfn)
>> +{
>> +	return 0;
>> +}
>>   #endif
>>   
>>   /*
>> @@ -1668,8 +1688,16 @@ static void isolate_freepages(struct compact_control *cc)
>>   
>>   		page = pageblock_pfn_to_page(block_start_pfn, block_end_pfn,
>>   									zone);
>> -		if (!page)
>> +		if (!page) {
>> +			unsigned long next_pfn;
>> +
>> +			next_pfn = skip_offline_sections_reverse(block_start_pfn);
>> +			if (next_pfn)
>> +				block_start_pfn = max(pageblock_start_pfn(next_pfn),
>> +						      low_pfn);
>> +
>>   			continue;
>> +		}
>>   
>>   		/* Check the block is suitable for migration */
>>   		if (!suitable_migration_target(cc, page))

  reply	other threads:[~2023-07-10  9:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  8:51 [PATCH 1/2] mm: compaction: use the correct type of list for free pages Baolin Wang
2023-07-07  8:51 ` [PATCH 2/2] mm: compaction: skip the memory hole rapidly when isolating " Baolin Wang
2023-07-07 11:56   ` David Hildenbrand
2023-07-10  6:11   ` Huang, Ying
2023-07-10  9:26     ` Baolin Wang [this message]
2023-07-11  0:37       ` Huang, Ying
2023-07-07 11:52 ` [PATCH 1/2] mm: compaction: use the correct type of list for " 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=36747b09-8141-019f-85dd-59f3d4623ec1@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.