So effectively oom_adj only works as enable/disable switch, and since noIf nothing else, this would seem to reduce the number of processes for which the OOM coefficient of evil must be calculated.
one knows how to tune it, it is better to do not touch at all. And get
ssh killed. I believe if it is ever used then only to disable oom at
all, which is wrong, since task still may be killed but after some
others. My patch adds a simple priority for that based on the name of
the process, which are known to the administrators who maintain given
system.