summaryrefslogtreecommitdiff
path: root/mm
diff options
context:
space:
mode:
authorMartin Liu <liumartin@google.com>2021-06-11 14:38:35 +0800
committerMartin Liu <liumartin@google.com>2021-06-30 17:07:19 +0800
commit0253b1bf1a9d970f8ada691e99ea4ba258ee09a9 (patch)
tree810dc75243c31478cbb1894f4f90d7da593eafb0 /mm
parent496c0445d3db864500af64b60d87556d4ad23b5f (diff)
MM: fine tune vm parameters for GKI version
Since GKI, we have THP and watermarker boost feature. Those features will bump up min_free_kbytes as. THP: boot min_free_kbytes statically while mm init phase Watermark_boost_factor: dynamically boost min_free_kbytes when hitting fragmentation event. Both changes will increase watermarks level by a lot and might cause LMKD not work as our expectation. Let's reset the value to align with our legacy projects to clarify the issues. Once we get more pro and con data, we could enable them again. Also, we don't have limitation to access limited physical memory so we could reset lowmem_reserve_ratio to zero. Bug: 190571517 Bug: 189938926 Bug: 190732106 Test: cat vm parameters Signed-off-by: Martin Liu <liumartin@google.com> Change-Id: I128d2f298dc8b82e472344d0d5c5588ce8a60702 Merged-In: I128d2f298dc8b82e472344d0d5c5588ce8a60702
Diffstat (limited to 'mm')
-rw-r--r--mm/pixel-mm-gki.rc6
1 files changed, 6 insertions, 0 deletions
diff --git a/mm/pixel-mm-gki.rc b/mm/pixel-mm-gki.rc
index 188c30c..ebeb236 100644
--- a/mm/pixel-mm-gki.rc
+++ b/mm/pixel-mm-gki.rc
@@ -12,5 +12,11 @@
# See the License for the specific language governing permissions and
# limitations under the License.
+on init
+ # memory reserve tuning
+ write /proc/sys/vm/watermark_boost_factor 0
+ write /proc/sys/vm/min_free_kbytes 27386
+ write /proc/sys/vm/lowmem_reserve_ratio "0 0 0"
+
on property:sys.boot_completed=1
chmod 444 /sys/kernel/debug/page_owner