lkml.org 
[lkml]   [2012]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRE: [PATCH 3.2.0-rc1 3/3] Used Memory Meter pseudo-device module
On Mon, 9 Jan 2012, leonid.moiseichuk@nokia.com wrote:

> 1.1. Pekka Enberg
> > However, from VM point of view, both have the exact same
> > functionality: detect when we reach low memory condition
> > (for some configurable threshold) and notify userspace or kernel
> > subsystem about it.
>
> Well, I cannot say that SIGKILL is a notification. From kernel side
> maybe. But Android OOM uses different memory tracking rules. From my
> opinion OOM killer should be as reliable as default is but functionality
> Android OOM killer does should be done in user space by some "smart
> killer" which closes application correct way (save data, notify user
> etc.). It heavily depends from product design.
>

I'm not sure why you need to detect low memory thresholds if you're not
interested in using the memory controller, why not just use the oom killer
delay that I suggested earlier and allow userspace to respond to
conditions when you are known to failed reclaim and require that something
be killed? Userspace should be able to make sane decisions or trigger
external knobs to be able to free memory much better than having the
kernel handling signals or notification to individual applications.

> 1.7. David Rientjes
> > This is just a side-note but as this information is meant to be consumed by userspace you have the option of hooking
> > into the mm_page_alloc tracepoint. You get the same information about how many pages are allocated or freed. I accept
> > that it will probably be a bit slower but on the plus side it'll be backwards compatible and you don't need a kernel
> > patch for it.
>

I didn't write that.


\
 
 \ /
  Last update: 2012-01-09 11:11    [W:0.086 / U:4.916 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site