From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: Anton Vorontsov <anton.vorontsov@linaro.org>
Cc: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>,
"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>,
"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 12:34:24 -0500 [thread overview]
Message-ID: <4EEF75A0.2080503@gmail.com> (raw)
In-Reply-To: <4EEF74AC.1060503@gmail.com>
>> + read_lock(&tasklist_lock);
>
> Crazy inefficient. mere slab shrinker shouldn't take tasklist_lock.
> Imagine if tasks are much plenty...
>
> Moreover, if system have plenty file cache, any process shouldn't killed
> at all! That's fundamental downside of this patch.
In addition, this code is reused a lot of code of oom-killer. But it is
bad idea. oom killer is really exceptional case. then it don't pay
attention faster processing. But, no free memory is not rare. we don't
have much free memory EVERY TIME. because we have file cache.
--
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>
prev parent reply other threads:[~2011-12-19 17:34 UTC|newest]
Thread overview: 23+ 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 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
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 [this message]
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=4EEF75A0.2080503@gmail.com \
--to=kosaki.motohiro@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anton.vorontsov@linaro.org \
--cc=arve@android.com \
--cc=gregkh@suse.de \
--cc=john.stultz@linaro.org \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).