From: Vlastimil Babka <vbabka@suse.cz>
To: js1304@gmail.com, Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [RFC PATCH 5/5] mm/compaction: run the compaction whenever fragmentation ratio exceeds the threshold
Date: Thu, 19 Jan 2017 14:39:54 +0100 [thread overview]
Message-ID: <835a0481-33ae-94fd-b84d-0ea394d66866@suse.cz> (raw)
In-Reply-To: <1484291673-2239-6-git-send-email-iamjoonsoo.kim@lge.com>
On 01/13/2017 08:14 AM, js1304@gmail.com wrote:
> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> Until now, we invoke the compaction whenever allocation request is stall
> due to non-existence of the high order freepage. It is effective since we
> don't need a high order freepage in usual and cost of maintaining
> high order freepages is quite high. However, it increases latency of high
> order allocation request and decreases success rate if allocation request
> cannot use the reclaim/compaction. Since there are some workloads that
> require high order freepage to boost the performance, it is a matter of
> trade-off that we prepares high order freepage in advance. Now, there is
> no way to prepare high order freepages, we cannot consider this trade-off.
> Therefore, this patch introduces a way to invoke the compaction when
> necessary to manage trade-off.
>
> Implementation is so simple. There is a theshold to invoke the full
> compaction. If fragmentation ratio reaches this threshold in given order,
> we ask the full compaction to kcompactd with a hope that it restores
> fragmentation ratio.
>
> If fragmentation ratio is unchanged or worse after full compaction,
> further compaction attempt would not be useful. So, this patch
> stops the full compaction in this case until the situation changes
> to avoid useless compaction effort.
>
> Now, there is no scientific code to detect the situation change.
> kcompactd's full compaction would be re-enabled when lower order
> triggers kcompactd wake-up or time limit (a second) is passed.
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
So, as you expected, I'm not thrilled about the tunables :) And also the
wakeups from allocator hotpaths. Otherwise I'll wait with discussing
details until we get some consensus on usecases and metrics.
--
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-01-19 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 7:14 [RFC PATCH 0/5] pro-active compaction js1304
2017-01-13 7:14 ` [RFC PATCH 1/5] mm/vmstat: retrieve suitable free pageblock information just once js1304
2017-01-19 10:47 ` Vlastimil Babka
2017-01-23 3:17 ` Joonsoo Kim
2017-01-19 11:51 ` Michal Hocko
2017-01-19 12:06 ` Vlastimil Babka
2017-01-13 7:14 ` [RFC PATCH 2/5] mm/vmstat: rename variables/functions about buddyinfo js1304
2017-01-13 7:14 ` [RFC PATCH 3/5] mm: introduce exponential moving average to unusable free index js1304
2017-01-19 12:52 ` Vlastimil Babka
2017-01-23 5:27 ` Joonsoo Kim
2017-01-13 7:14 ` [RFC PATCH 4/5] mm/vmstat: introduce /proc/fraginfo to get fragmentation stat stably js1304
2017-01-13 7:14 ` [RFC PATCH 5/5] mm/compaction: run the compaction whenever fragmentation ratio exceeds the threshold js1304
2017-01-19 13:39 ` Vlastimil Babka [this message]
2017-01-13 9:24 ` [RFC PATCH 0/5] pro-active compaction Michal Hocko
2017-01-17 0:48 ` 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=835a0481-33ae-94fd-b84d-0ea394d66866@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=rientjes@google.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