Re: [RFC][PATCH 3/8] mem_notify v5: introduce /dev/mem_notify new device (the core of this patch series)

2008-01-24 Thread Daniel Spång
Hi KOSAKI, On 1/24/08, KOSAKI Motohiro <[EMAIL PROTECTED]> wrote: > +#define PROC_WAKEUP_GUARD (10*HZ) [...] > + timeout = info->last_proc_notify + PROC_WAKEUP_GUARD; If only one or a few processes are using the system I think 10 seconds is a little long time to wait before they get the no

Re: [RFC][PATCH 4/5] memory_pressure_notify() caller

2008-01-18 Thread Daniel Spång
On 1/17/08, KOSAKI Motohiro <[EMAIL PROTECTED]> wrote: > Hi Daniel > > > > Thank you for good point out! > > > Could you please post your test program and reproduced method? > > > > Sure: > > > > 1. Fill almost all available memory with page cache in a system without > > swap. > > 2. Run attached

Re: [RFC][PATCH 3/5] add /dev/mem_notify device

2008-01-16 Thread Daniel Spång
On 1/16/08, Pavel Machek <[EMAIL PROTECTED]> wrote: > On Wed 2008-01-16 02:13:32, Marcelo Tosatti wrote: > > On Wed, Jan 16, 2008 at 10:57:16AM +0900, KOSAKI Motohiro wrote: > > > Hi Pavel > > > > > > > > err = poll(&pollfds, 1, -1); // wake up at low memory > > > > > > > > > > ...

Re: [RFC][PATCH 4/5] memory_pressure_notify() caller

2008-01-16 Thread Daniel Spång
On 1/16/08, KOSAKI Motohiro <[EMAIL PROTECTED]> wrote: > Hi Daniel > > > > > The notification fires after only ~100 MB allocated, i.e., when page > > > > reclaim is beginning to nag from page cache. Isn't this a bit early? > > > > Repeating the test with swap enabled results in a notification after

Re: [RFC][PATCH 4/5] memory_pressure_notify() caller

2008-01-15 Thread Daniel Spång
On 1/15/08, Rik van Riel <[EMAIL PROTECTED]> wrote: > > On Tue, 15 Jan 2008 23:55:17 +0100 > "Daniel Spång" <[EMAIL PROTECTED]> wrote: > > > The notification fires after only ~100 MB allocated, i.e., when page > > reclaim is beginning to nag from pag

Re: [RFC][PATCH 4/5] memory_pressure_notify() caller

2008-01-15 Thread Daniel Spång
Hi, On 1/15/08, KOSAKI Motohiro <[EMAIL PROTECTED]> wrote: > the notification point to happen whenever the VM moves an > anonymous page to the inactive list - this is a pretty good indication > that there are unused anonymous pages present which will be very likely > swapped out soon. > +

Re: Out of memory management in embedded systems

2007-09-28 Thread Daniel Spång
On 9/28/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote: > > On Fri, 28 Sep 2007, [iso-8859-1] Daniel Spång wrote: > > > On 9/28/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote: > >> > >> On Fri, 28 Sep 2007, [iso-8859-1] Daniel Spång

Re: Out of memory management in embedded systems

2007-09-28 Thread Daniel Spång
On 9/28/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote: > > On Fri, 28 Sep 2007, [iso-8859-1] Daniel Spång wrote: > > > On 9/28/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote: > >> > >> But an embedded system contains all the software t

Re: Out of memory management in embedded systems

2007-09-28 Thread Daniel Spång
On 9/28/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote: > > On Fri, 28 Sep 2007, [iso-8859-1] Daniel Spång wrote: > > > Applications with dynamic input and dynamic memory usage have some > > issues with the current overcommitting kernel. A high memory usage >

Out of memory management in embedded systems

2007-09-28 Thread Daniel Spång
Applications with dynamic input and dynamic memory usage have some issues with the current overcommitting kernel. A high memory usage situation eventually results in that a process is killed by the OOM killer. This is especially evident in swapless embedded systems with limited memory and no swap a