| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 15 Nov 2010 10:57:35 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: David Rientjes <rientjes@...gle.com> Cc: "Figo.zhang" <zhangtianfei@...dcoretech.com>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, "Figo.zhang" <figo1802@...il.com>, lkml <linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>, Andrew Morton <akpm@...l.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [PATCH] Revert oom rewrite series > 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists