| 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: <4F04B3F0.6080103@redhat.com> Date: Wed, 04 Jan 2012 15:17:52 -0500 From: Rik van Riel <riel@...hat.com> To: Greg KH <gregkh@...e.de> CC: Leonid Moiseichuk <leonid.moiseichuk@...ia.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, cesarb@...arb.net, kamezawa.hiroyu@...fujitsu.com, emunson@...bm.net, penberg@...nel.org, aarcange@...hat.com, mel@....ul.ie, rientjes@...gle.com, dima@...roid.com, rebecca@...roid.com, san@...gle.com, akpm@...ux-foundation.org, vesa.jaaskelainen@...ia.com, Minchan Kim <minchan@...hat.com>, KOSAKI Motohiro <kosaki.motohiro@...il.com> Subject: Re: [PATCH 3.2.0-rc1 0/3] Used Memory Meter pseudo-device and related changes in MM On 01/04/2012 02:56 PM, Greg KH wrote: > How does this compare with the lowmemorykiller.c driver from the android > developers that is currently in the linux-next tree? Also, the low memory notification that Kosaki-san has worked on, and which Minchan is looking at now. We seem to have many mechanisms under development, all aimed at similar goals. I believe it would be good to agree on one mechanism that could solve multiple of these goals at once, instead of sticking a handful of different partial solutions in the kernel... Exactly what is the problem you are trying to solve? -- All rights reversed -- 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