From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 15 Jan 2008 20:48:15 +0900 From: KOSAKI Motohiro Subject: Re: [RFC][PATCH 3/5] add /dev/mem_notify device In-Reply-To: <20080115112027.6120915b@lxorguk.ukuu.org.uk> References: <20080115195022.11A3.KOSAKI.MOTOHIRO@jp.fujitsu.com> <20080115112027.6120915b@lxorguk.ukuu.org.uk> Message-Id: <20080115202711.11A6.KOSAKI.MOTOHIRO@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Alan Cox Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Marcelo Tosatti , Daniel Spang , Rik van Riel , Andrew Morton List-ID: Hi Alan thank you for kindfull explain. > > > > 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 ? current wake up order is simply FIFO by poll(2) called. because the VM cannot know how much amount each process can do in free. the process rss and freeable memory is not proportional. thus I adopt wake up one after another until restoration memory shortage. > It also appears there is no way to wait for memory shortages (processes > that can free memory easily) only for memory to start appearing. poll() with never timeout don't fill your requirement? to be honest, maybe I don't understand your afraid yet. sorry. -kosaki -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org