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 v3 4/8] mm/compaction: correct comment of fast_find_migrateblock in isolate_migratepages
Date: Mon, 7 Aug 2023 17:42:10 +0800 [thread overview]
Message-ID: <7d687e10-32a8-1404-e714-4c6784e45f99@linux.alibaba.com> (raw)
In-Reply-To: <20230804110454.2935878-5-shikemeng@huaweicloud.com>
On 8/4/2023 7:04 PM, Kemeng Shi wrote:
> After 90ed667c03fe5 ("Revert "Revert "mm/compaction: fix set skip in
> fast_find_migrateblock"""), we remove skip set in fast_find_migrateblock.
> Correct comment that fast_find_block is used to avoid isolation_suitable
> check for pageblock returned from fast_find_migrateblock because
> fast_find_migrateblock will mark found pageblock skipped.
> Instead, comment that fast_find_block is used to avoid a redundant check
> of fast found pageblock which is already checked skip flag inside
> fast_find_migrateblock.
>
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
LGTM.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> ---
> mm/compaction.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> index 9a2f0bd5394a..4bf2dc936add 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -1988,9 +1988,9 @@ static isolate_migrate_t isolate_migratepages(struct compact_control *cc)
> block_start_pfn = cc->zone->zone_start_pfn;
>
> /*
> - * fast_find_migrateblock marks a pageblock skipped so to avoid
> - * the isolation_suitable check below, check whether the fast
> - * search was successful.
> + * fast_find_migrateblock() has already ensured the pageblock is not
> + * set with a skipped flag, so to avoid the isolation_suitable check
> + * below again, check whether the fast search was successful.
> */
> fast_find_block = low_pfn != cc->migrate_pfn && !cc->fast_search_fail;
>
next prev parent reply other threads:[~2023-08-07 9:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 11:04 [PATCH v3 0/8] Fixes and cleanups to compaction Kemeng Shi
2023-08-04 11:04 ` [PATCH v3 1/8] mm/compaction: avoid missing last page block in section after skip offline sections Kemeng Shi
2023-08-07 9:41 ` Baolin Wang
2023-08-04 11:04 ` [PATCH v3 2/8] mm/compaction: correct last_migrated_pfn update in compact_zone Kemeng Shi
2023-08-04 11:04 ` [PATCH v3 3/8] mm/compaction: skip page block marked skip in isolate_migratepages_block Kemeng Shi
2023-08-04 11:04 ` [PATCH v3 4/8] mm/compaction: correct comment of fast_find_migrateblock in isolate_migratepages Kemeng Shi
2023-08-07 9:42 ` Baolin Wang [this message]
2023-08-04 11:04 ` [PATCH v3 5/8] mm/compaction: correct comment of cached migrate pfn update Kemeng Shi
2023-08-04 11:04 ` [PATCH v3 6/8] mm/compaction: correct comment to complete migration failure Kemeng Shi
2023-08-04 11:04 ` [PATCH v3 7/8] mm/compaction: remove unnecessary return for void function Kemeng Shi
2023-08-04 11:04 ` [PATCH v3 8/8] mm/compaction: only set skip flag if cc->no_set_skip_hint is false Kemeng Shi
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=7d687e10-32a8-1404-e714-4c6784e45f99@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
all inboxes | Powered by JetHome®