linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kemeng Shi <shikemeng@huaweicloud.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, mgorman@techsingularity.net,
	willy@infradead.org, david@redhat.com
Subject: Re: [PATCH 1/8] mm/compaction: avoid missing last page block in section after skip offline sections
Date: Tue, 1 Aug 2023 16:42:34 +0800	[thread overview]
Message-ID: <7b42d243-c62f-856e-2b8c-ba43528528f0@huaweicloud.com> (raw)
In-Reply-To: <d5d3dc39-c825-f040-1c1e-ae6c53921331@linux.alibaba.com>



on 8/1/2023 4:01 PM, Baolin Wang wrote:
> 
> 
> On 8/1/2023 2:08 PM, Kemeng Shi wrote:
>>
>>
>> on 8/1/2023 11:53 AM, Baolin Wang wrote:
>>>
>>>
>>> On 8/1/2023 10:36 AM, Kemeng Shi wrote:
>>>>
>>>>
>>>> on 8/1/2023 10:18 AM, Kemeng Shi wrote:
>>>>>
>>>>>
>>>>> on 7/31/2023 8:01 PM, Baolin Wang wrote:
>>>>>>
>>>>>>
>>>>>> On 7/29/2023 1:10 AM, Kemeng Shi wrote:
>>>>>>> skip_offline_sections_reverse will return the last pfn in found online
>>>>>>> section. Then we set block_start_pfn to start of page block which
>>>>>>> contains the last pfn in section. Then we continue, move one page
>>>>>>> block forward and ignore the last page block in the online section.
>>>>>>> Make block_start_pfn point to first page block after online section to fix
>>>>>>> this:
>>>>>>> 1. make skip_offline_sections_reverse return end pfn of online section,
>>>>>>> i.e. pfn of page block after online section.
>>>>>>> 2. assign block_start_pfn with next_pfn.
>>>>>>>
>>>>>>> Fixes: f63224525309 ("mm: compaction: skip the memory hole rapidly when isolating free pages")
>>>>>>> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
>>>>>>> ---
>>>>>>>     mm/compaction.c | 5 ++---
>>>>>>>     1 file changed, 2 insertions(+), 3 deletions(-)
>>>>>>>
>>>>>>> diff --git a/mm/compaction.c b/mm/compaction.c
>>>>>>> index 9b7a0a69e19f..ce7841363b12 100644
>>>>>>> --- a/mm/compaction.c
>>>>>>> +++ b/mm/compaction.c
>>>>>>> @@ -259,7 +259,7 @@ static unsigned long skip_offline_sections_reverse(unsigned long start_pfn)
>>>>>>>           while (start_nr-- > 0) {
>>>>>>>             if (online_section_nr(start_nr))
>>>>>>> -            return section_nr_to_pfn(start_nr) + PAGES_PER_SECTION - 1;
>>>>>>> +            return section_nr_to_pfn(start_nr + 1);
>>>>>>
>>>>>> This is incorrect, you returned the start pfn of this section.
>>>>>>
>>>>>>>         }
>>>>>>>           return 0;
>>>>>>> @@ -1670,8 +1670,7 @@ static void isolate_freepages(struct compact_control *cc)
>>>>>>>                   next_pfn = skip_offline_sections_reverse(block_start_pfn);
>>>>>>>                 if (next_pfn)
>>>>>>> -                block_start_pfn = max(pageblock_start_pfn(next_pfn),
>>>>>>> -                              low_pfn);
>>>>>>> +                block_start_pfn = max(next_pfn, low_pfn);
>>>>>>
>>>>>> 'block_start_pfn' should be pageblock aligned. If the 'next_pfn' is not pageblock-aligned (though this is not the common case), we should skip it.
>>>>>>
>>>>>> But if the 'next_pfn' is pageblock-aligned, yes, the commit f63224525309 still ignores the last pageblock, which is not right. So I think it should be:
>>>>>> block_start_pfn = pageblock_aligned(next_pfn) ? : pageblock_start_pfn(next_pfn);
>>>>>> block_start_pfn = max(block_start_pfn, low_pfn);
>>>>>>
>>>>> Hi Baolin, thanks for reply! As skip_offline_sections_reverse is based
>>>>> on skip_offline_sections. I make the assumption that section is pageblock
>>>>> aligned based on that we use section start from skip_offline_sections as
>>>>> block_start_fpn without align check.
>>>>> If section size is not pageblock aligned in real world, the pageblock aligned
>>>>> check should be added to skip_offline_sections and skip_offline_sections_reverse.
>>>>> If no one is against this, I will fix this in next version. THanks!
>>>>>
>>>> More information of aligment of section. For powerpc arch, we have SECTION_SIZE_BITS
>>>> with 24 while PAGE_SHIFT could be configured to 18.
>>>> Pageblock order is (18 + MAX_ORDER) which coule be 28 and is > SECTION_SZIE_BITS 24,
>>>
>>> The maximum pageblock order is MAX_ORDER. But after thinking more, I think return the start pfn or end pfn of a section is okay, and it should be aligned to a pageblock order IIUC.
>>>
>> Right, I mixed up the unit.
>>> So I think your change is good:
>>> + block_start_pfn = max(next_pfn, low_pfn);
>>>
>>> But in skip_offline_sections_reverse(), we should still return the last pfn of the online section.
>>>
>> Sure, then we should assign block_start_pfn with following change. Is this good to you?
>> -                block_start_pfn = max(pageblock_start_pfn(next_pfn),
>> +         block_start_pfn = max(pageblock_end_pfn(next_pfn),
>>                                low_pfn);
> 
> The last pfn of a section is already section aligned, so I think no need to call pageblock_end_pfn(), just like your original change is okay to me.
> block_start_pfn = max(next_pfn, low_pfn);
> 
> 
Um, if we keep "block_start_pfn = max(next_pfn, low_pfn);", should we also keep
returning end of section "section_nr_to_pfn(start_nr + 1);" instead of original last
pfn of the section "section_nr_to_pfn(start_nr) + PAGES_PER_SECTION - 1;" which seems
not aligned.
Assume SECTION_SIZE_BITS = 27, PAGE_SHIFT = 12, pageblock order = 10
Last pfn of the section 0 is 0x7fff, end pfn of section 0 is 0x8000. The last pfn
is not aligned.
Please tell me if I misunderstand anything. Thanks!

-- 
Best wishes
Kemeng Shi



  reply	other threads:[~2023-08-01  8:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 17:10 [PATCH 0/8] Fixes and cleanups to compaction Kemeng Shi
2023-07-28 17:10 ` [PATCH 2/8] mm/compaction: correct last_migrated_pfn update in compact_zone Kemeng Shi
2023-08-01  2:09   ` Baolin Wang
2023-08-01  2:19     ` Kemeng Shi
2023-07-28 17:10 ` [PATCH 4/8] mm/compaction: remove stale fast_find_block flag in isolate_migratepages Kemeng Shi
2023-08-01  2:42   ` Baolin Wang
2023-08-01  3:24     ` Kemeng Shi
2023-08-01  3:34       ` Baolin Wang
2023-08-01  3:48         ` Kemeng Shi
2023-08-01  8:15           ` Baolin Wang
2023-07-28 17:10 ` [PATCH 5/8] mm/compaction: corret comment of cached migrate pfn update Kemeng Shi
2023-07-28 10:35   ` David Hildenbrand
2023-08-01  2:45   ` Baolin Wang
2023-07-28 17:10 ` [PATCH 6/8] mm/compaction: correct comment to complete migration failure Kemeng Shi
2023-07-28 17:10 ` [PATCH 8/8] mm/compaction: only set skip flag if cc->no_set_skip_hint is false Kemeng Shi
2023-07-28 10:33   ` David Hildenbrand
2023-08-01  3:02   ` Baolin Wang
     [not found] ` <20230728171037.2219226-2-shikemeng@huaweicloud.com>
2023-07-28 10:41   ` [PATCH 1/8] mm/compaction: avoid missing last page block in section after skip offline sections David Hildenbrand
2023-07-29  2:23     ` Kemeng Shi
2023-07-31 12:01   ` Baolin Wang
2023-08-01  2:18     ` Kemeng Shi
2023-08-01  2:36       ` Kemeng Shi
2023-08-01  3:53         ` Baolin Wang
2023-08-01  6:08           ` Kemeng Shi
2023-08-01  8:01             ` Baolin Wang
2023-08-01  8:42               ` Kemeng Shi [this message]
2023-08-01  9:32                 ` Baolin Wang
2023-08-01 12:33                   ` Kemeng Shi
2023-08-02  1:11                     ` Baolin Wang
2023-08-02  1:26                       ` Kemeng Shi
     [not found] ` <20230728171037.2219226-8-shikemeng@huaweicloud.com>
2023-07-28 10:30   ` [PATCH 7/8] mm/compaction: remove unnecessary return for void function David Hildenbrand
2023-08-01  2:53   ` 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=7b42d243-c62f-856e-2b8c-ba43528528f0@huaweicloud.com \
    --to=shikemeng@huaweicloud.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=willy@infradead.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