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: Thu, 28 Jan 2010 00:16:36 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>, rientjes@...gle.com, minchan.kim@...il.com, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "balbir@...ux.vnet.ibm.com" <balbir@...ux.vnet.ibm.com> Subject: Re: [PATCH v3] oom-kill: add lowmem usage aware oom kill handling > Now, /proc/<pid>/oom_score and /proc/<pid>/oom_adj are used by servers. And embedded, and some desktops (including some neat experimental hacks where windows slowly get to be bigger bigger oom targes the longer they've been non-focussed) > For my customers, I don't like oom black magic. I'd like to recommend to > use memcg, of course ;) But lowmem oom cannot be handled by memcg, well. > So I started from this. I can't help feeling this is the wrong approach. IFF we are running out of low memory pages then killing stuff for that reason is wrong to begin with except in extreme cases and those extreme cases are probably also cases the kill won't help. If we have a movable user page (even an mlocked one) then if there is space in other parts of memory (ie the OOM is due to a single zone problem) we should *never* be killing in the first place, we should be moving the page. The mlock case is a bit hairy but the non mlock case is exactly the same sequence of operations as a page out and page in somewhere else skipping the widdling on the disk bit in the middle. There are cases we can't do that - eg if the kernel has it pinned for DMA, but in that case OOM isn't going to recover the page either - at least not until the DMA or whatever unpins it (at which point you could just move it). Am I missing something fundamental here ? 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