linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Shantanu Goel <sgoel01@yahoo.com>,
	Mel Gorman <mgorman@techsingularity.net>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] vmscan: fix zone balance check in prepare_kswapd_sleep
Date: Fri, 10 Feb 2017 14:11:50 +0100	[thread overview]
Message-ID: <901a8aba-b211-9a1a-f4a3-4ad70ae8918b@suse.cz> (raw)
In-Reply-To: <68644e18-ed8d-0559-4ac2-fb3162f6ba67@yahoo.com>

On 02/07/2017 01:16 AM, Shantanu Goel wrote:
> Hi,
>
> On 02/06/2017 11:17 AM, Mel Gorman wrote:
>
>> On Sun, Feb 05, 2017 at 12:46:20PM +0000, Shantanu Goel wrote:
>>> On 4.9.7 kswapd is failing to wake up kcompactd due to a mismatch in the zone balance check between balance_pgdat() and prepare_kswapd_sleep().  balance_pgdat() returns as soon as a single zone satisfies the allocation but prepare_kswapd_sleep() requires all zones to do the same.  This causes prepare_kswapd_sleep() to never succeed except in the order == 0 case and consequently, wakeup_kcompactd() is never called.  On my machine prior to apply this patch, the state of compaction from /proc/vmstat looked this way after a day and a half of uptime:
>>>
>>> compact_migrate_scanned 240496
>>> compact_free_scanned 76238632
>>> compact_isolated 123472
>>> compact_stall 1791
>>> compact_fail 29
>>> compact_success 1762
>>> compact_daemon_wake 0
>>>
>>>
>>> After applying the patch and about 10 hours of uptime the state looks like this:
>>>
>>> compact_migrate_scanned 59927299
>>> compact_free_scanned 2021075136
>>> compact_isolated 640926
>>> compact_stall 4
>>> compact_fail 2
>>> compact_success 2
>>> compact_daemon_wake 5160

I've just seen similar results in a test, so you can add:

Tested-by: Vlastimil Babka <vbabka@suse.cz>

Thanks!

--
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>

      parent reply	other threads:[~2017-02-10 13:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <719282122.1183240.1486298780546.ref@mail.yahoo.com>
2017-02-05 12:46 ` Shantanu Goel
2017-02-06  3:19   ` Hillf Danton
2017-02-06  8:31   ` Michal Hocko
2017-02-06 11:51     ` Vlastimil Babka
2017-02-06 16:17   ` Mel Gorman
2017-02-06 17:43     ` Vlastimil Babka
2017-02-06 22:24       ` Mel Gorman
2017-02-07  0:16     ` Shantanu Goel
2017-02-07  9:54       ` Mel Gorman
2017-02-10 13:11       ` Vlastimil Babka [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=901a8aba-b211-9a1a-f4a3-4ad70ae8918b@suse.cz \
    --to=vbabka@suse.cz \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=sgoel01@yahoo.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