linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vlastimil Babka <vbabka@suse.cz>, Mel Gorman <mgorman@suse.de>,
	David Rientjes <rientjes@google.com>,
	Rik van Riel <riel@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	stable@vger.kernel.org
Subject: [PATCH 1/4] mm/compaction: fix wrong order check in compact_finished()
Date: Mon,  8 Dec 2014 16:16:17 +0900	[thread overview]
Message-ID: <1418022980-4584-2-git-send-email-iamjoonsoo.kim@lge.com> (raw)
In-Reply-To: <1418022980-4584-1-git-send-email-iamjoonsoo.kim@lge.com>

What we want to check here is whether there is highorder freepage
in buddy list of other migratetype in order to steal it without
fragmentation. But, current code just checks cc->order which means
allocation request order. So, this is wrong.

Without this fix, non-movable synchronous compaction below pageblock order
would not stopped until compaction is complete, because migratetype of most
pageblocks are movable and high order freepage made by compaction is usually
on movable type buddy list.

There is some report related to this bug. See below link.

http://www.spinics.net/lists/linux-mm/msg81666.html

Although the issued system still has load spike comes from compaction,
this makes that system completely stable and responsive according to
his report.

stress-highalloc test in mmtests with non movable order 7 allocation doesn't
show any notable difference in allocation success rate, but, it shows more
compaction success rate and reduced elapsed time.

Compaction success rate (Compaction success * 100 / Compaction stalls, %)
18.47 : 28.94

Elapsed time (sec)
1429 : 1411

Cc: <stable@vger.kernel.org>
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
---
 mm/compaction.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/compaction.c b/mm/compaction.c
index c9ee464..1a5f465 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -1105,7 +1105,7 @@ static int __compact_finished(struct zone *zone, struct compact_control *cc,
 			return COMPACT_PARTIAL;
 
 		/* Job done if allocation would set block type */
-		if (cc->order >= pageblock_order && area->nr_free)
+		if (order >= pageblock_order && area->nr_free)
 			return COMPACT_PARTIAL;
 	}
 
-- 
1.7.9.5

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-12-08  7:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08  7:16 [PATCH 0/4] enhance compaction success rate Joonsoo Kim
2014-12-08  7:16 ` Joonsoo Kim [this message]
2014-12-08  9:06   ` [PATCH 1/4] mm/compaction: fix wrong order check in compact_finished() Vlastimil Babka
2014-12-08  7:16 ` [PATCH 2/4] mm/page_alloc: expands broken freepage to proper buddy list when steal Joonsoo Kim
2014-12-08  9:29   ` Vlastimil Babka
2014-12-10  6:38     ` Joonsoo Kim
2014-12-10  9:55       ` Vlastimil Babka
2015-01-27  7:35       ` Vlastimil Babka
2015-01-27  8:34         ` Joonsoo Kim
2015-01-27  8:36           ` Vlastimil Babka
2014-12-08  7:16 ` [PATCH 3/4] mm/compaction: enhance compaction finish condition Joonsoo Kim
2014-12-08  9:34   ` Vlastimil Babka
2014-12-10  6:46     ` Joonsoo Kim
2014-12-08  7:16 ` [PATCH 4/4] mm/compaction: stop the isolation when we isolate enough freepage Joonsoo Kim
2014-12-08  9:59   ` Vlastimil Babka
2014-12-10  7:00     ` Joonsoo Kim
2014-12-10 15:19       ` Vlastimil Babka
2014-12-11  3:09         ` Joonsoo Kim
2014-12-08  9:16 ` [PATCH 0/4] enhance compaction success rate Vlastimil Babka
2014-12-10  6:36   ` Joonsoo Kim

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=1418022980-4584-2-git-send-email-iamjoonsoo.kim@lge.com \
    --to=iamjoonsoo.kim@lge.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    /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