[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EEF6240.9020107@gmail.com>
Date: Mon, 19 Dec 2011 11:11:44 -0500
From: KOSAKI Motohiro <kosaki.motohiro@...il.com>
To: Anton Vorontsov <anton.vorontsov@...aro.org>
CC: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Arve Hjønnevåg
<arve@...roid.com>, Rik van Riel <riel@...hat.com>,
Pavel Machek <pavel@....cz>,
Greg Kroah-Hartman <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
David Rientjes <rientjes@...gle.com>,
Michal Hocko <mhocko@...e.cz>,
John Stultz <john.stultz@...aro.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: Android low memory killer vs. memory pressure notifications
> - Use memory controller cgroup (CGROUP_MEM_RES_CTLR) notifications from
> the kernel side, plus userland "manager" that would kill applications.
>
> 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.
>
> 0.5% doesn't sound too bad, but 5MB does, quite a little bit. So,
> mem_cg feels like an overkill for this simple task (see the driver at
> the very bottom).
Kamezawa-san, Is 20bytes/page still correct now? If I remember
correctly, you improved space efficiency of memcg.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists