From: "Hillf Danton" <hillf.zj@alibaba-inc.com>
To: 'Vlastimil Babka' <vbabka@suse.cz>,
'Mel Gorman' <mgorman@techsingularity.net>
Cc: 'Andrew Morton' <akpm@linux-foundation.org>,
'Shantanu Goel' <sgoel01@yahoo.com>, 'Chris Mason' <clm@fb.com>,
'Johannes Weiner' <hannes@cmpxchg.org>,
'LKML' <linux-kernel@vger.kernel.org>,
'Linux-MM' <linux-mm@kvack.org>
Subject: Re: [PATCH 3/3] mm, vmscan: Prevent kswapd sleeping prematurely due to mismatched classzone_idx
Date: Tue, 21 Feb 2017 12:10:34 +0800 [thread overview]
Message-ID: <012701d28bf8$7380d920$5a828b60$@alibaba-inc.com> (raw)
In-Reply-To: <d4e3317b-5ae8-f61c-4d71-5a74a4014cc7@suse.cz>
On February 21, 2017 12:34 AM Vlastimil Babka wrote:
> On 02/16/2017 09:21 AM, Hillf Danton wrote:
> > Right, but the order-3 request can also come up while kswapd is active and
> > gives up order-5.
>
> "Giving up on order-5" means it will set sc.order to 0, go to sleep (assuming
> order-0 watermarks are OK) and wakeup kcompactd for order-5. There's no way how
> kswapd could help an order-3 allocation at that point - it's up to kcompactd.
>
cpu0 cpu1
give up order-5
fall back to order-0
wake up kswapd for order-3
wake up kswapd for order-5
fall in sleep
wake up kswapd for order-3
what order would
we try?
It is order-5 in the patch.
Given the fresh new world without hike ban after napping,
one tenth second or 3 minutes, we feel free IMHO to select
any order and go another round of reclaiming pages.
thanks
Hillf
--
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>
next prev parent reply other threads:[~2017-02-21 4:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 9:22 [PATCH 0/3] Reduce amount of time kswapd sleeps prematurely Mel Gorman
2017-02-15 9:22 ` [PATCH 1/3] mm, vmscan: fix zone balance check in prepare_kswapd_sleep Mel Gorman
2017-02-16 2:50 ` Hillf Danton
2017-02-22 7:00 ` Minchan Kim
2017-02-23 15:05 ` Mel Gorman
2017-02-24 1:17 ` Minchan Kim
2017-02-24 9:11 ` Mel Gorman
2017-02-27 6:16 ` Minchan Kim
2017-02-15 9:22 ` [PATCH 2/3] mm, vmscan: Only clear pgdat congested/dirty/writeback state when balanced Mel Gorman
2017-02-15 9:22 ` [PATCH 3/3] mm, vmscan: Prevent kswapd sleeping prematurely due to mismatched classzone_idx Mel Gorman
2017-02-16 6:23 ` Hillf Danton
2017-02-16 8:10 ` Mel Gorman
2017-02-16 8:21 ` Hillf Danton
2017-02-16 9:32 ` Mel Gorman
2017-02-20 16:34 ` Vlastimil Babka
2017-02-21 4:10 ` Hillf Danton [this message]
2017-02-20 16:42 ` Vlastimil Babka
2017-02-23 15:01 ` Mel Gorman
2017-03-01 9:04 ` Vlastimil Babka
2017-02-15 20:30 ` [PATCH 0/3] Reduce amount of time kswapd sleeps prematurely Andrew Morton
2017-02-15 21:29 ` Mel Gorman
2017-02-15 21:56 ` Andrew Morton
2017-02-15 22:15 ` Mel Gorman
2017-02-15 22:00 ` Vlastimil Babka
2017-03-09 7:56 [PATCH 0/3] Reduce amount of time kswapd sleeps prematurely v2 Mel Gorman
2017-03-09 7:56 ` [PATCH 3/3] mm, vmscan: Prevent kswapd sleeping prematurely due to mismatched classzone_idx Mel Gorman
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='012701d28bf8$7380d920$5a828b60$@alibaba-inc.com' \
--to=hillf.zj@alibaba-inc.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=sgoel01@yahoo.com \
--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