822709 - oom_score_adjs used on gonk don't correspond to integer oom_adj's

Status: RESOLVED INVALID

(Core :: Hardware Abstraction Layer (HAL), defect)

Description

[Justin Lebar (not reading bugmail)]

From bug 821440 comment 18:

Unless the kernel is doing something weird, it turns out that none of our oom_score_adj's correspond to integer oom_adj's.

  $ adb shell
  # echo 3 > /proc/1766/oom_adj; cat /proc/1766/oom_score_adj
  176
  # echo 4 > /proc/1766/oom_adj; cat /proc/1766/oom_score_adj
  235

So 200 is not an integer oom_adj.  But neither is 400, which we currently use for bg processes:

  # echo 6 > /proc/1766/oom_adj; cat /proc/1766/oom_score_adj     
  352
  # echo 7 > /proc/1766/oom_adj; cat /proc/1766/oom_score_adj     
  411

and neither is 67, which we use for fg processes:

  # echo 1 > /proc/1766/oom_adj; cat /proc/1766/oom_score_adj     
  58
  # echo 2 > /proc/1766/oom_adj; cat /proc/1766/oom_score_adj     
  117

I think we need to fix GonkHal.cpp::OomAdjOfOomScoreAdj, too.

Comment 1

[Justin Lebar (not reading bugmail)]

And this is invalid; see bug 821440 comment 23.