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
| ||
|
Message-Id: <20071026140201.ae52757c.akpm@linux-foundation.org> Date: Fri, 26 Oct 2007 14:02:01 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Marcelo Tosatti <marcelo@...ck.org> Cc: linux-kernel@...r.kernel.org, drepper@...hat.com, riel@...hat.com, Martin Bligh <mbligh@...igh.org>, linux-mm@...ck.org Subject: Re: OOM notifications On Thu, 18 Oct 2007 16:15:31 -0400 Marcelo Tosatti <marcelo@...ck.org> wrote: > Hi, > > AIX contains the SIGDANGER signal to notify applications to free up some > unused cached memory: > > http://www.ussg.iu.edu/hypermail/linux/kernel/0007.0/0901.html > > There have been a few discussions on implementing such an idea on Linux, > but nothing concrete has been achieved. > > On the kernel side Rik suggested two notification points: "about to > swap" (for desktop scenarios) and "about to OOM" (for embedded-like > scenarios). > > With that assumption in mind it would be necessary to either have two > special devices for notification, or somehow indicate both events > through the same file descriptor. > > Comments are more than welcome. Martin was talking about some mad scheme wherin you'd create a bunch of pseudo files (say, /proc/foo/0, /proc/foo/1, ..., /proc/foo/9) and each one would become "ready" when the MM scanning priority reaches 10%, 20%, ... 100%. Obviously there would need to be a lot of abstraction to unhook a permanent userspace feature from a transient kernel implementation, but the basic idea is that a process which wants to know when the VM is getting into the orange zone would select() on the file "7" and a process which wants to know when the VM is getting into the red zone would select on file "9". It get more complicated with NUMA memory nodes and cgroup memory controllers. - 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