Messages in this thread | | | Date | Mon, 19 Dec 2011 11:24:18 -0500 | From | Rik van Riel <> | Subject | Re: Android low memory killer vs. memory pressure notifications |
| |
On 12/19/2011 11:16 AM, KOSAKI Motohiro wrote: > (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.
And the reason for that, I suspect, is that the "proper" implementation changes the VM by so much that it would never have been merged in the first place...
-- All rights reversed
| |