[lkml]   [2011]   [Dec]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Android low memory killer vs. memory pressure notifications
(12/19/11 5:39 AM), Alan Cox wrote:
>> The main downside of this approach is that mem_cg needs 20 bytes per
>> page (on a 32 bit machine). So on a 32 bit machine with 4K pages
>> that's approx. 0.5% of RAM, or, in other words, 5MB on a 1GB machine.
> The obvious question would be why? Would fixing memcg make more sense ?

Just historical reason. Initial memcg implement by IBM was just crap.
People need very long time to fix it.

> The only problem I see with having a user space manager is that manager
> probably has to be mlock to avoid awkward fail cases and that may in fact
> make it smaller kernel side.

 \ /
  Last update: 2011-12-19 17:19    [W:0.103 / U:1.980 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site