lkml.org 
[lkml]   [2012]   [May]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH v4] vmevent: Implement greater-than attribute state and one-shot mode
Date
> -----Original Message-----
> From: ext Minchan Kim [mailto:minchan@kernel.org]
> Sent: 02 May, 2012 08:04
> To: Anton Vorontsov
> Cc: KOSAKI Motohiro; Rik van Riel; Pekka Enberg; Moiseichuk Leonid (Nokia-
...
> I think hardest problem in low mem notification is how to define _lowmem
> situation_.
> We all guys (server, desktop and embedded) should reach a conclusion on
> define lowmem situation before progressing further implementation
> because each part can require different limits.
> Hopefully, I want it.
>
> What is the best situation we can call it as "low memory"?

That depends on what user-space can do. In n9 case [1] we can handle some OOM/slowness-prevention and actions e.g. close background applications, stop prestarted apps,
flush browser/graphics caches in applications and do all the things kernel even don't know about. This set of activities usually comes as memory management design.

From another side, polling by re-scan vmstat data using procfs might be performance heavy and for sure - use-time disaster.

Leonid
[1] http://maemo.gitorious.org/maemo-tools/libmemnotify - yes, not ideal but it works and quite well isolated code.
\
 
 \ /
  Last update: 2012-05-02 09:21    [W:0.080 / U:0.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site