lkml.org 
[lkml]   [2012]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH 3.2.0-rc1 3/3] Used Memory Meter pseudo-device module
Date
> -----Original Message-----
> From: ext David Rientjes [mailto:rientjes@google.com]
> Sent: 13 January, 2012 12:06
> To: Moiseichuk Leonid (Nokia-MP/Helsinki)
...
> > Why? That is expected that product tested and tuned properly,
> > applications fixed, and at least no apps installed which might consume
> > 100 MB in second or two.
>
> I'm trying to make this easy for you, if you haven't noticed.
Thanks, I did.

> Your memory threshold, as proposed, will have values that are tied directly to the
> implementation of the VM in the kernel when its under memory pressure
> and that implementation evolves at a constant rate.

Not sure that I understand this statement. Free/Used/Active page sets are properties of any VM.
I have a new implementation but it is in testing now. I do not see any relation to VM implementation except statistics and it could be extended with
"virtual values" which are suitable for user-space e.g. active page set. It could be extended with something else if someone needs it.
The thresholds are set by user-space and individual for applications which likes to be informed.

> mlock() the memory that your userspace monitoring needs to send signals to
> applications, whether those signals are handled to free memory internally or
> its SIGTERM or SIGKILL.

Mlocked memory should be avoid as much as possible because efficiency rate is lowest possible and makes situation for non-mlocked pages even worse.
You cannot mlock whole UI only most critical parts.
Thus, handling time in case of 3rd party apps will be not controllable, User will observe it as device jam/hang/freeze.


\
 
 \ /
  Last update: 2012-01-13 12:55    [from the cache]
©2003-2011 Jasper Spaans