From: Frank Rowand <frank.rowand@am.sony.com>
To: Anton Vorontsov <anton.vorontsov@linaro.org>
Cc: "Rowand, Frank" <Frank_Rowand@sonyusa.com>,
"David Rientjes" <rientjes@google.com>,
"KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>,
"Michal Hocko" <mhocko@suse.cz>,
"Arve Hjønnevåg" <arve@android.com>,
"Rik van Riel" <riel@redhat.com>, "Pavel Machek" <pavel@ucw.cz>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"John Stultz" <john.stultz@linaro.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"tbird20d@gmail.com" <tbird20d@gmail.com>
Subject: Re: Android low memory killer vs. memory pressure notifications
Date: Tue, 20 Dec 2011 18:30:41 -0800 [thread overview]
Message-ID: <4EF144D1.2020807@am.sony.com> (raw)
In-Reply-To: <20111221020723.GA5214@oksana.dev.rtsoft.ru>
On 12/20/11 18:07, Anton Vorontsov wrote:
> On Tue, Dec 20, 2011 at 05:14:18PM -0800, Frank Rowand wrote:
< snip >
>> And for embedded and for real-time, some of us do not want cgroups to be
>> a mandatory thing. We want it to remain configurable. My personal
>> interest is in keeping the latency of certain critical paths (especially
>> in the scheduler) short and consistent.
>
> Much thanks for your input! That would be quite strong argument for going
> with /dev/mem_notify approach. Do you have any specific numbers how cgroups
> makes scheduler latencies worse?
Sorry, I don't have specific numbers. And the numbers would be workload
specific anyway.
-Frank
--
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: Frank Rowand <frank.rowand@am.sony.com>
To: Anton Vorontsov <anton.vorontsov@linaro.org>
Cc: "Rowand, Frank" <Frank_Rowand@sonyusa.com>,
"David Rientjes" <rientjes@google.com>,
"KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>,
"Michal Hocko" <mhocko@suse.cz>,
"Arve Hjønnevåg" <arve@android.com>,
"Rik van Riel" <riel@redhat.com>, "Pavel Machek" <pavel@ucw.cz>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"John Stultz" <john.stultz@linaro.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"tbird20d@gmail.com" <tbird20d@gmail.com>
Subject: Re: Android low memory killer vs. memory pressure notifications
Date: Tue, 20 Dec 2011 18:30:41 -0800 [thread overview]
Message-ID: <4EF144D1.2020807@am.sony.com> (raw)
In-Reply-To: <20111221020723.GA5214@oksana.dev.rtsoft.ru>
On 12/20/11 18:07, Anton Vorontsov wrote:
> On Tue, Dec 20, 2011 at 05:14:18PM -0800, Frank Rowand wrote:
< snip >
>> And for embedded and for real-time, some of us do not want cgroups to be
>> a mandatory thing. We want it to remain configurable. My personal
>> interest is in keeping the latency of certain critical paths (especially
>> in the scheduler) short and consistent.
>
> Much thanks for your input! That would be quite strong argument for going
> with /dev/mem_notify approach. Do you have any specific numbers how cgroups
> makes scheduler latencies worse?
Sorry, I don't have specific numbers. And the numbers would be workload
specific anyway.
-Frank
next prev parent reply other threads:[~2011-12-21 2:31 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
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 [this message]
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=4EF144D1.2020807@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=Frank_Rowand@sonyusa.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=hannes@cmpxchg.org \
--cc=john.stultz@linaro.org \
--cc=kamezawa.hiroyu@jp.fujitsu.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=riel@redhat.com \
--cc=rientjes@google.com \
--cc=tbird20d@gmail.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.