From: Rik van Riel <riel@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Anton Vorontsov" <anton.vorontsov@linaro.org>,
"KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Pavel Machek" <pavel@ucw.cz>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Rientjes" <rientjes@google.com>,
"Michal Hocko" <mhocko@suse.cz>,
"John Stultz" <john.stultz@linaro.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Android low memory killer vs. memory pressure notifications
Date: Mon, 19 Dec 2011 11:24:18 -0500 [thread overview]
Message-ID: <4EEF6532.3090201@redhat.com> (raw)
In-Reply-To: <4EEF6360.4000306@gmail.com>
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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Anton Vorontsov" <anton.vorontsov@linaro.org>,
"KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Pavel Machek" <pavel@ucw.cz>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Rientjes" <rientjes@google.com>,
"Michal Hocko" <mhocko@suse.cz>,
"John Stultz" <john.stultz@linaro.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Android low memory killer vs. memory pressure notifications
Date: Mon, 19 Dec 2011 11:24:18 -0500 [thread overview]
Message-ID: <4EEF6532.3090201@redhat.com> (raw)
In-Reply-To: <4EEF6360.4000306@gmail.com>
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
next prev parent reply other threads:[~2011-12-19 16:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 2:53 Android low memory killer vs. memory pressure notifications Anton Vorontsov
2011-12-19 2:53 ` Anton Vorontsov
2011-12-19 7:48 ` Minchan Kim
2011-12-19 7:48 ` Minchan Kim
2011-12-19 19:05 ` David Rientjes
2011-12-19 19:05 ` David Rientjes
2011-12-19 10:39 ` Alan Cox
2011-12-19 10:39 ` Alan Cox
2011-12-19 16:16 ` KOSAKI Motohiro
2011-12-19 16:16 ` KOSAKI Motohiro
2011-12-19 16:24 ` Rik van Riel [this message]
2011-12-19 16:24 ` Rik van Riel
2011-12-19 12:12 ` Michal Hocko
2011-12-19 12:12 ` Michal Hocko
2011-12-19 19:12 ` David Rientjes
2011-12-19 19:12 ` David Rientjes
2011-12-20 14:56 ` Anton Vorontsov
2011-12-20 14:56 ` Anton Vorontsov
2011-12-20 21:36 ` David Rientjes
2011-12-20 21:36 ` David Rientjes
2011-12-21 0:28 ` Anton Vorontsov
2011-12-21 0:28 ` Anton Vorontsov
2011-12-21 1:14 ` Frank Rowand
2011-12-21 1:14 ` Frank Rowand
2011-12-21 2:07 ` Anton Vorontsov
2011-12-21 2:07 ` Anton Vorontsov
2011-12-21 2:30 ` Frank Rowand
2011-12-21 2:30 ` Frank Rowand
2011-12-21 23:41 ` Anton Vorontsov
2011-12-21 23:41 ` Anton Vorontsov
2011-12-22 1:16 ` KOSAKI Motohiro
2011-12-22 1:16 ` KOSAKI Motohiro
2011-12-22 18:53 ` Frank Rowand
2011-12-22 18:53 ` Frank Rowand
2011-12-21 2:50 ` David Rientjes
2011-12-21 2:50 ` David Rientjes
2011-12-20 2:16 ` Anton Vorontsov
2011-12-20 2:16 ` Anton Vorontsov
2011-12-19 16:11 ` KOSAKI Motohiro
2011-12-19 16:11 ` KOSAKI Motohiro
2011-12-20 0:30 ` Hiroyuki Kamezawa
2011-12-20 0:30 ` Hiroyuki Kamezawa
2011-12-19 17:30 ` KOSAKI Motohiro
2011-12-19 17:30 ` KOSAKI Motohiro
2011-12-19 17:34 ` KOSAKI Motohiro
2011-12-19 17:34 ` KOSAKI Motohiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EEF6532.3090201@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton.vorontsov@linaro.org \
--cc=arve@android.com \
--cc=gregkh@suse.de \
--cc=john.stultz@linaro.org \
--cc=kosaki.motohiro@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=pavel@ucw.cz \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.