lmkd: Disable critical thrashing limit by default
Critical thrashing limit determines the balance between how much thrashing should be tolerated before killing a perceptible app. This threshold might differ between devices, therefore we disable critical thrashing limit by default allowing each device to set it individually. This is done to prevent excessive kills of perceptible apps. Bug: 194199500 Signed-off-by: Suren Baghdasaryan <surenb@google.com> Change-Id: Idd1715564c3727b09fcb0a109ab3d6bae9d0b99a
This commit is contained in:
parent
a01f251ff2
commit
e1ffef4e36
2
lmkd.cpp
2
lmkd.cpp
|
|
@ -3407,7 +3407,7 @@ static void update_props() {
|
|||
thrashing_limit_decay_pct = clamp(0, 100, property_get_int32("ro.lmk.thrashing_limit_decay",
|
||||
low_ram_device ? DEF_THRASHING_DECAY_LOWRAM : DEF_THRASHING_DECAY));
|
||||
thrashing_critical_pct = max(0, property_get_int32("ro.lmk.thrashing_limit_critical",
|
||||
thrashing_limit_pct * 2));
|
||||
INT_MAX));
|
||||
swap_util_max = clamp(0, 100, property_get_int32("ro.lmk.swap_util_max", 100));
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue