Because NOTHING breaks with the new mapping. Eight months later since
this was initially proposed on linux-mm, you still cannot show a single
example that depended on the exponential mapping of oom_adj. I'm not
going to continue responding to your criticism about this point since your
argument is completely and utterly baseless.
That would require the userspace tunable to be adjusted anytime a task's
mempolicy changes, its nodemask changes, it's cpuset attachment changes,
its mems change, a memcg limit changes, etc. The only constant is the
task's priority, and the current oom_score_adj implementation preserves
that unless explicitly changed later by the user. I completely understand
that you may not have a use for this.
--
