From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Kemeng Shi <shikemeng@huaweicloud.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, mgorman@techsingularity.net,
david@redhat.com
Subject: Re: [PATCH 4/9] mm/compaction: simplify pfn iteration in isolate_freepages_range
Date: Tue, 15 Aug 2023 18:07:58 +0800 [thread overview]
Message-ID: <3729c50f-6f8e-2548-8932-f39045402299@linux.alibaba.com> (raw)
In-Reply-To: <43b726c1-3ea6-9acc-d4e4-c7deabcf7ecd@huaweicloud.com>
On 8/15/2023 5:32 PM, Kemeng Shi wrote:
>
>
> on 8/15/2023 4:38 PM, Baolin Wang wrote:
>>
>>
>> On 8/5/2023 7:07 PM, Kemeng Shi wrote:
>>> We call isolate_freepages_block in strict mode, continuous pages in
>>> pageblock will be isolated if isolate_freepages_block successed.
>>> Then pfn + isolated will point to start of next pageblock to scan
>>> no matter how many pageblocks are isolated in isolate_freepages_block.
>>> Use pfn + isolated as start of next pageblock to scan to simplify the
>>> iteration.
>>
>> IIUC, the isolate_freepages_block() can isolate high-order free pages, which means the pfn + isolated can be larger than the block_end_pfn. So in your patch, the 'block_start_pfn' and 'block_end_pfn' can be in different pageblocks, that will break pageblock_pfn_to_page().
>>
> In for update statement, we always update block_start_pfn to pfn and
I mean, you changed to:
1) pfn += isolated;
2) block_start_pfn = pfn;
3) block_end_pfn = pfn + pageblock_nr_pages;
But in 1) pfn + isolated can go outside of the currnet pageblock if
isolating a high-order page, for example, located in the middle of the
next pageblock. So that the block_start_pfn can point to the middle of
the next pageblock, not the start position. Meanwhile after 3), the
block_end_pfn can point another pageblock. Or I missed something else?
> update block_end_pfn to pfn + pageblock_nr_pages. So they should point
> to the same pageblock. I guess you missed the change to update of
> block_end_pfn. :)
>>>
>>> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
>>> ---
>>> mm/compaction.c | 14 ++------------
>>> 1 file changed, 2 insertions(+), 12 deletions(-)
>>>
>>> diff --git a/mm/compaction.c b/mm/compaction.c
>>> index 684f6e6cd8bc..8d7d38073d30 100644
>>> --- a/mm/compaction.c
>>> +++ b/mm/compaction.c
>>> @@ -733,21 +733,11 @@ isolate_freepages_range(struct compact_control *cc,
>>> block_end_pfn = pageblock_end_pfn(pfn);
>>> for (; pfn < end_pfn; pfn += isolated,
>>> - block_start_pfn = block_end_pfn,
>>> - block_end_pfn += pageblock_nr_pages) {
>>> + block_start_pfn = pfn,
>>> + block_end_pfn = pfn + pageblock_nr_pages) {
>>> /* Protect pfn from changing by isolate_freepages_block */
>>> unsigned long isolate_start_pfn = pfn;
>>> - /*
>>> - * pfn could pass the block_end_pfn if isolated freepage
>>> - * is more than pageblock order. In this case, we adjust
>>> - * scanning range to right one.
>>> - */
>>> - if (pfn >= block_end_pfn) {
>>> - block_start_pfn = pageblock_start_pfn(pfn);
>>> - block_end_pfn = pageblock_end_pfn(pfn);
>>> - }
>>> -
>>> block_end_pfn = min(block_end_pfn, end_pfn);
>>> if (!pageblock_pfn_to_page(block_start_pfn,
>>
next prev parent reply other threads:[~2023-08-15 10:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 11:07 [PATCH 0/9] Fixes and cleanups to compaction Kemeng Shi
2023-08-05 3:14 ` Matthew Wilcox
2023-08-05 4:07 ` Kemeng Shi
2023-08-05 11:07 ` [PATCH 2/9] mm/compaction: call list_is_{first}/{last} more intuitively in move_freelist_{head}/{tail} Kemeng Shi
2023-08-15 7:49 ` Baolin Wang
2023-08-05 11:07 ` [PATCH 5/9] mm/compaction: remove repeat compact_blockskip_flush check in reset_isolation_suitable Kemeng Shi
2023-08-15 8:42 ` Baolin Wang
2023-08-05 11:07 ` [PATCH 6/9] mm/compaction: rename is_via_compact_memory to compaction_with_allocation_order Kemeng Shi
2023-08-15 8:58 ` Baolin Wang
2023-08-15 12:04 ` Kemeng Shi
2023-08-19 12:14 ` Baolin Wang
2023-08-22 1:51 ` Kemeng Shi
2023-08-24 2:20 ` Baolin Wang
2023-08-05 11:07 ` [PATCH 7/9] mm/compaction: factor out code to test if we should run compaction for target order Kemeng Shi
2023-08-15 8:53 ` Baolin Wang
2023-08-15 12:10 ` Kemeng Shi
2023-08-19 12:27 ` Baolin Wang
2023-08-22 1:57 ` Kemeng Shi
2023-08-24 2:25 ` Baolin Wang
2023-08-24 2:59 ` Kemeng Shi
2023-08-05 11:07 ` [PATCH 9/9] mm/compaction: call compaction_suit_allocation_order in kcompactd_do_work Kemeng Shi
[not found] ` <20230805110711.2975149-2-shikemeng@huaweicloud.com>
2023-08-05 17:11 ` [PATCH 1/9] mm/compaction: use correct list in move_freelist_{head}/{tail} Andrew Morton
2023-08-07 0:37 ` Kemeng Shi
2023-08-15 7:16 ` Baolin Wang
[not found] ` <20230805110711.2975149-4-shikemeng@huaweicloud.com>
2023-08-15 8:28 ` [PATCH 3/9] mm/compaction: correctly return failure with bogus compound_order in strict mode Baolin Wang
2023-08-15 9:22 ` Kemeng Shi
[not found] ` <20230805110711.2975149-5-shikemeng@huaweicloud.com>
2023-08-15 8:38 ` [PATCH 4/9] mm/compaction: simplify pfn iteration in isolate_freepages_range Baolin Wang
2023-08-15 9:32 ` Kemeng Shi
2023-08-15 10:07 ` Baolin Wang [this message]
2023-08-15 10:37 ` Kemeng Shi
2023-08-19 11:58 ` Baolin Wang
2023-08-22 1:37 ` Kemeng Shi
2023-08-24 2:19 ` 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=3729c50f-6f8e-2548-8932-f39045402299@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=shikemeng@huaweicloud.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