From: Oscar Salvador <osalvador@suse.de>
To: Rei Yamamoto <yamamoto.rei@jp.fujitsu.com>
Cc: akpm@linux-foundation.org, mgorman@techsingularity.net,
vvghjk1234@gmail.com, aquini@redhat.com, ddutile@redhat.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm, compaction: fast_find_migrateblock() should return pfn in the target zone
Date: Fri, 13 May 2022 09:54:44 +0200 [thread overview]
Message-ID: <Yn4OxDIsl3OfB+6W@localhost.localdomain> (raw)
In-Reply-To: <20220511044300.4069-1-yamamoto.rei@jp.fujitsu.com>
On Wed, May 11, 2022 at 01:43:00PM +0900, Rei Yamamoto wrote:
> Prevent returning a pfn outside the target zone in case that not
> aligned with pageblock boundary.
> Otherwise isolate_migratepages_block() would handle pages not in
> the target zone.
>
> Signed-off-by: Rei Yamamoto <yamamoto.rei@jp.fujitsu.com>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
> ---
> mm/compaction.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> index fe915db6149b..de42b8e48758 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -1858,6 +1858,8 @@ static unsigned long fast_find_migrateblock(struct compact_control *cc)
>
> update_fast_start_pfn(cc, free_pfn);
> pfn = pageblock_start_pfn(free_pfn);
> + if (pfn < cc->zone->zone_start_pfn)
> + pfn = cc->zone->zone_start_pfn;
> cc->fast_search_fail = 0;
> found_block = true;
> set_pageblock_skip(freepage);
> --
> 2.27.0
>
>
--
Oscar Salvador
SUSE Labs
prev parent reply other threads:[~2022-05-13 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 4:43 [PATCH] mm, compaction: fast_find_migrateblock() should return pfn in the target zone Rei Yamamoto
2022-05-11 6:25 ` Miaohe Lin
2022-05-11 7:07 ` Rei Yamamoto
2022-05-11 9:26 ` Miaohe Lin
2022-05-12 1:47 ` Rei Yamamoto
2022-05-12 2:20 ` Andrew Morton
2022-05-12 2:27 ` Miaohe Lin
2022-05-12 4:27 ` Rei Yamamoto
2022-05-12 20:49 ` Andrew Morton
2022-05-13 4:11 ` Rei Yamamoto
2022-05-13 21:01 ` Andrew Morton
2022-05-16 2:41 ` Rei Yamamoto
2022-05-12 9:04 ` Mel Gorman
2022-05-13 7:54 ` Oscar Salvador [this message]
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=Yn4OxDIsl3OfB+6W@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=ddutile@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=vvghjk1234@gmail.com \
--cc=yamamoto.rei@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).