mm: set default watermark_boost_factor value to 0
Upstream: no Watermark boost factor controls the level of reclaim when memory is being fragmented. The intent is that compaction has less work to do in the future and to increase the success rate of future high-order allocations such as SLUB allocations, THP and hugetlbfs pages. However, it wakeup kswapd to do defragmentation, the action caused performance jitter in many cases without enough gain. In some distributions like Debian, also set the default boost fator to 0 to disable the feature. WXG Story of compaction cause performance jitter: https://doc.weixin.qq.com/doc/w3_AIAAcwacAAYudo6ERcUQMiNUbmvzb?scode=AJEAIQdfAAoeO7AbqSAYQATQaYAJg Signed-off-by: Haisu Wang <haisuwang@tencent.com> Signed-off-by: Kairui Song <kasong@tencent.com> Signed-off-by: Zeng Jingxiang <linuszeng@tencent.com> Reviewed-by: Jianping Liu <frankjpliu@tencent.com>
This commit is contained in:
parent
b03afc0d33
commit
2fc4b0e9c0
|
@ -290,7 +290,7 @@ const char * const migratetype_names[MIGRATE_TYPES] = {
|
|||
|
||||
int min_free_kbytes = 1024;
|
||||
int user_min_free_kbytes = -1;
|
||||
static int watermark_boost_factor __read_mostly = 15000;
|
||||
static int watermark_boost_factor __read_mostly;
|
||||
static int watermark_scale_factor = 10;
|
||||
|
||||
/* movable_zone is the "real" zone pages in ZONE_MOVABLE are taken from */
|
||||
|
|
Loading…
Reference in New Issue