Reduce oom score adj of Dbus Broker
Dbus broker uses 1.2GB and dosent get earlyoom killed until every other process is killed
due to its oom_score_adj value of -900. Reducing it to -600 to allow other processes
to stay alive when dbus broker uses >90% of the system's memory.
I see a 60 oom score decrease for every 100 adjust. Currently using 95% of the system's
memory has a badness score of 662. Now it should have a score of 842, which should be killed
early on in the earlyoom kill streak.
I see around 670 as the average badness score of other processes on the system.
Tested:
Messed around w oom score adj on real machine.
fusion2:
938ee1f0-6bc1-3d59-906a-5b3fa3ebf1db
d3520ed4-34e5-3769-95fb-bc66888327ce
dbc9a17c-df97-3dbe-8c39-00d568e517df
0c2880d3-2bf5-3faa-a772-fbb371e105ad
0c2880d3-2bf5-3faa-a772-fbb371e105ad
Test failure on one of the platforms.
Google-Bug-Id: 438738723
Change-Id: I7d48e15a73993c6d0c33bc0a2fec69696c90baa0
Signed-off-by: Edward Lee <edwarddl@google.com>
diff --git a/meta-gbmc-staging b/meta-gbmc-staging
index d012112..086a8be 160000
--- a/meta-gbmc-staging
+++ b/meta-gbmc-staging
@@ -1 +1 @@
-Subproject commit d012112f1165b7f85ff03e7bddf309b4c1269095
+Subproject commit 086a8be5085a2adf89b8c0b6eaf2bd4e134833b9
