From 72637ea3639ab2e98988340a4c461ebb3b54a360 Mon Sep 17 00:00:00 2001 From: Martin Liu Date: Tue, 2 May 2023 17:18:12 +0800 Subject: [PATCH] adjust applying watermark_scale_factor timing We should apply watermark_sclae_factor after boot complete. Otherwise, extra_free_kbytes.sh might overwrite it and this also aligns with previous projects' timing. Bug: 278075546 Test: boot and check watermark_scale_factor Change-Id: I7989fd1e8cd968193577300b0f83a829bdeb037d Signed-off-by: Martin Liu --- conf/init.zuma.rc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/conf/init.zuma.rc b/conf/init.zuma.rc index 86f95579..84b424e5 100644 --- a/conf/init.zuma.rc +++ b/conf/init.zuma.rc @@ -105,9 +105,6 @@ on init write /sys/block/zram0/comp_algorithm lz77eh write /proc/sys/vm/page-cluster 0 - # Adjust watermark level - write /proc/sys/vm/watermark_scale_factor 200 - # Some user code relies on ro.boot.hardware.revision setprop ro.boot.hardware.revision ${ro.revision} @@ -718,6 +715,9 @@ on property:sys.boot_completed=1 swapon_all /vendor/etc/fstab.${ro.board.platform} write /proc/sys/vm/swappiness 100 + # Adjust watermark level + write /proc/sys/vm/watermark_scale_factor 200 + # Back to default VM settings write /proc/sys/vm/dirty_expire_centisecs 3000 write /proc/sys/vm/dirty_background_ratio 10