linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Chuyi Zhou <zhouchuyi@bytedance.com>, linux-mm@kvack.org
Subject: Re: [PATCH v3] mm/compaction: fix set skip in fast_find_migrateblock
Date: Thu, 14 Jul 2022 12:50:20 +0100	[thread overview]
Message-ID: <20220714115020.GA3563@techsingularity.net> (raw)
In-Reply-To: <20220713082814.bed234e00d7f5ceb3858352a@linux-foundation.org>

On Wed, Jul 13, 2022 at 08:28:14AM -0700, Andrew Morton wrote:
> (cc Mel)
> 
> On Wed, 13 Jul 2022 14:20:09 +0800 Chuyi Zhou <zhouchuyi@bytedance.com> wrote:
> 
> > From: zhouchuyi <zhouchuyi@bytedance.com>
> > 
> > When we successfully find a pageblock in fast_find_migrateblock(),
> > the block will be set skip-flag through set_pageblock_skip(). However,
> > when entering isolate_migratepages_block(), the whole pageblock will
> > be skipped due to the branch
> > 'if (!valid_page && IS_ALIGNED(low_pfn, pageblock_nr_pages))'.
> > Eventually we will goto isolate_abort and isolate nothing. That cause
> > fast_find_migrateblock useless.
> > 

It's not very clear *why* this failed from the changelog because
superficially !valid_page will be true for the first pageblock and there
is a reasonable expectation it will be aligned. Is the following accurate
based on your analysis?

	However, when entering isolate_migratepages_block(), the first
	pageblock will be skipped in the branch 'if (!valid_page &&
	IS_ALIGNED(low_pfn, pageblock_nr_pages))' as isolation_suitable
	returns true due to the skip bit set by fast_find_migrateblock().

If so, please update the changelog as a reviewer handling backports may
wonder what exactly is wrong with that branch.

Second, what guarantees a block returned by fast_find that is not
aligned gets marked skipped after it is scanned? The set_pageblock_skip
is only called when there is a valid page and it may not be set if
!IS_ALIGNED(low_pfn). Is something like this untested hunk also necessary?

diff --git a/mm/compaction.c b/mm/compaction.c
index 1f89b969c12b..112346b2f716 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -888,8 +888,9 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
 		 * COMPACT_CLUSTER_MAX at a time so the second call must
 		 * not falsely conclude that the block should be skipped.
 		 */
-		if (!valid_page && IS_ALIGNED(low_pfn, pageblock_nr_pages)) {
-			if (!isolation_suitable(cc, page)) {
+		if (!valid_page) {
+			if (IS_ALIGNED(low_pfn, pageblock_nr_pages) &&
+			    !isolation_suitable(cc, page)) {
 				low_pfn = end_pfn;
 				page = NULL;
 				goto isolate_abort;

> > In this Patch, when we find a suitable pageblock in fast_find_
> > migrateblock, we do noting but let isolate_migratepages_block
> > to set skip flag to the pageblock after scan it. Normally,
> > we would isolate some pages from the fast-find block.
> > 
> > I use mmtest/thpscale-madvhugepage test it. Here is the result:
> >                             baseline               patch
> > Amean     fault-both-1      1331.66 (   0.00%)     1261.04 *   5.30%*
> > Amean     fault-both-3      1383.95 (   0.00%)     1191.69 *  13.89%*
> > Amean     fault-both-5      1568.13 (   0.00%)     1445.20 *   7.84%*
> > Amean     fault-both-7      1819.62 (   0.00%)     1555.13 *  14.54%*
> > Amean     fault-both-12     1106.96 (   0.00%)     1149.43 *  -3.84%*
> > Amean     fault-both-18     2196.93 (   0.00%)     1875.77 *  14.62%*
> > Amean     fault-both-24     2642.69 (   0.00%)     2671.21 *  -1.08%*
> > Amean     fault-both-30     2901.89 (   0.00%)     2857.32 *   1.54%*
> > Amean     fault-both-32     3747.00 (   0.00%)     3479.23 *   7.15%*
> > 
> > Fixes: 70b44595eafe9 ("mm, compaction: use free lists to quickly locate a migration source")
> > 
> > Signed-off-by: zhouchuyi <zhouchuyi@bytedance.com>

No need for a newline between Fixes and Signed-off-by. The Signed-off-by
should have your full name, not a username.

-- 
Mel Gorman
SUSE Labs


  reply	other threads:[~2022-07-14 12:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13  6:20 Chuyi Zhou
2022-07-13 15:28 ` Andrew Morton
2022-07-14 11:50   ` Mel Gorman [this message]
2022-07-15 15:26     ` Chuyi Zhou
2022-07-19  8:28       ` Mel Gorman
2022-08-15  1:24         ` Andrew Morton
     [not found]           ` <70a434b2-7f1c-7fad-a7b7-cb038a13fd2c@bytedance.com>
2022-08-15  3:22             ` Chuyi Zhou
     [not found]         ` <7d2bbb38-a96c-8212-8f89-915cd2c8668f@bytedance.com>
2022-08-17  3:10           ` Chuyi Zhou
2023-01-09 19:43         ` Vlastimil Babka
2023-01-11 14:21           ` Mel Gorman
2023-01-13 17:13             ` Vlastimil Babka

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=20220714115020.GA3563@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=zhouchuyi@bytedance.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