> The goal was to make the oom killer heuristic as predictable as possible > and to kill the most memory-hogging task to avoid having to recall it and > needlessly kill several tasks. Meta question - why is that a good thing. In a desktop environment it's frequently wrong, in a server environment it is often wrong. We had this before where people spend months fiddling with the vm and make it work slightly differently and it suits their workload, then other workloads go downhill. Then the cycle repeats. > You have full control over disabling a task from being considered with > oom_score_adj just like you did with oom_adj. Since oom_adj is > deprecated for two years, you can even use the old interface until then. Which changeset added it to the Documentation directory as deprecated ? Alan -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>