| 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: <20080115112027.6120915b@lxorguk.ukuu.org.uk> Date: Tue, 15 Jan 2008 11:20:27 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> Cc: kosaki.motohiro@...fujitsu.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Marcelo Tosatti <marcelo@...ck.org>, Daniel Spang <daniel.spang@...il.com>, Rik van Riel <riel@...hat.com>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [RFC][PATCH 3/5] add /dev/mem_notify device On Tue, 15 Jan 2008 19:59:02 +0900 KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote: > > > > the core of this patch series. > > > add /dev/mem_notify device for notification low memory to user process. > > > > As you only wake one process how would you use this API from processes > > which want to monitor and can free memory under load. Also what fairness > > guarantees are there... > > Sorry, I don't make sense what you mean fairness. > Could you tell more? If you have two processes each waiting on mem_notify is it not possible that one of them will keep being the one woken up and the other will remain stuck ? It also appears there is no way to wait for memory shortages (processes that can free memory easily) only for memory to start appearing. -- 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