linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Rei Yamamoto <yamamoto.rei@jp.fujitsu.com>, <akpm@linux-foundation.org>
Cc: <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: Wed, 11 May 2022 14:25:34 +0800	[thread overview]
Message-ID: <2c2900eb-886a-5bbe-f7c7-9d74a6399893@huawei.com> (raw)
In-Reply-To: <20220511044300.4069-1-yamamoto.rei@jp.fujitsu.com>

On 2022/5/11 12:43, 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.
> 

IIUC, the sole caller isolate_migratepages will ensure the pfn won't outside
the target zone. So the below code change might not be necessary. Or am I miss
something ?

Thanks!

> Signed-off-by: Rei Yamamoto <yamamoto.rei@jp.fujitsu.com>
> ---
>  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);
> 



  reply	other threads:[~2022-05-11  6:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  4:43 Rei Yamamoto
2022-05-11  6:25 ` Miaohe Lin [this message]
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

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=2c2900eb-886a-5bbe-f7c7-9d74a6399893@huawei.com \
    --to=linmiaohe@huawei.com \
    --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