linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frank.rowand@am.sony.com>
To: Anton Vorontsov <anton.vorontsov@linaro.org>
Cc: "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
Subject: Re: Android low memory killer vs. memory pressure notifications
Date: Tue, 20 Dec 2011 17:14:18 -0800	[thread overview]
Message-ID: <4EF132EA.7000300@am.sony.com> (raw)
In-Reply-To: <20111221002853.GA11504@oksana.dev.rtsoft.ru>

On 12/20/11 16:28, Anton Vorontsov wrote:
> On Tue, Dec 20, 2011 at 01:36:00PM -0800, David Rientjes wrote:
>> On Tue, 20 Dec 2011, Anton Vorontsov wrote:
>>
>>> Hm, assuming that metadata is no longer an issue, why do you think avoiding
>>> cgroups would be a good idea?
>>>
>>
>> It's helpful for certain end users, particularly those in the embedded 
>> world, to be able to disable as many config options as possible to reduce 
>> the size of kernel image as much as possible, so they'll want a minimal 
>> amount of kernel functionality that allows such notifications.  Keep in 
>> mind that CONFIG_CGROUP_MEM_RES_CTLR is not enabled by default because of 
>> this (enabling it, CONFIG_RESOURCE_COUNTERS, and CONFIG_CGROUPS increases 
>> the size of the kernel text by ~1%),
> 
> So for 2MB kernel that's about 20KB of an additional text... This seems
> affordable, especially as a trade-off for the things that cgroups may
> provide.

A comment from http://lkml.indiana.edu/hypermail/linux/kernel/1102.1/00412.html:

"I care about 5K. (But honestly, I don't actively hunt stuff less than
10K in size, because there's too many of them to chase, currently)."

> 
> The fact is, for desktop and server Linux, cgroups slowly becomes a
> mandatory thing. And the reason for this is that cgroups mechanism
> provides some very useful features (in an extensible way, like plugins),
> i.e. a way to manage and track processes and its resources -- which is the
> main purpose of cgroups.

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.

-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>

  reply	other threads:[~2011-12-21  1:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19  2:53 Anton Vorontsov
2011-12-19  7:48 ` Minchan Kim
2011-12-19 19:05   ` David Rientjes
2011-12-19 10:39 ` Alan Cox
2011-12-19 16:16   ` KOSAKI Motohiro
2011-12-19 16:24     ` Rik van Riel
2011-12-19 12:12 ` Michal Hocko
2011-12-19 19:12   ` David Rientjes
2011-12-20 14:56     ` Anton Vorontsov
2011-12-20 21:36       ` David Rientjes
2011-12-21  0:28         ` Anton Vorontsov
2011-12-21  1:14           ` Frank Rowand [this message]
2011-12-21  2:07             ` Anton Vorontsov
2011-12-21  2:30               ` Frank Rowand
2011-12-21 23:41                 ` Anton Vorontsov
2011-12-22  1:16             ` KOSAKI Motohiro
2011-12-22 18:53               ` Frank Rowand
2011-12-21  2:50           ` David Rientjes
2011-12-20  2:16   ` Anton Vorontsov
2011-12-19 16:11 ` KOSAKI Motohiro
2011-12-20  0:30   ` Hiroyuki Kamezawa
2011-12-19 17:30 ` 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=4EF132EA.7000300@am.sony.com \
    --to=frank.rowand@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox