From: David Rientjes <rientjes@google.com>
To: Simon Jeons <simon.jeons@gmail.com>
Cc: Jonathan Woithe <jwoithe@atrad.com.au>, linux-mm@kvack.org
Subject: Re: OOM triggered with plenty of memory free
Date: Tue, 19 Feb 2013 23:05:29 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1302192302270.27407@chino.kir.corp.google.com> (raw)
In-Reply-To: <5124641C.5020209@gmail.com>
On Wed, 20 Feb 2013, Simon Jeons wrote:
> I read drivers/staging/android/lowmemorykiller.c, it seems that android's oom
> just care about oom_score/oom_score_adj exported in /proc which will lead to
> good user experience, but who will set these values if users playing android
> mobiles? Is there userspace monitor process will do it? If the answer is yes,
> then how it determines one process is important or not?
>
It's up to userspace to determine how to adjust oom priorities for
processes, whether you're using the Android low memory killer or the
kernel oom killer. Many open source packages modify these values for
themselves directly, but any process can elevate the oom_score_adj value
for any other process making it more preferable for oom kill; processes
cannot lower oom_score_adj, itself included, unless it has the
SYS_RESOURCE capability. Everything else is left to userspace since the
kernel has no knowledge of what is important and what is not.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-02-20 7:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 3:10 Jonathan Woithe
2013-02-13 3:30 ` David Rientjes
2013-02-13 4:25 ` Jonathan Woithe
2013-02-13 15:14 ` Dave Hansen
2013-02-13 22:49 ` Jonathan Woithe
2013-02-21 6:01 ` Jonathan Woithe
2013-02-26 6:39 ` Jonathan Woithe
2013-02-26 15:26 ` Dave Hansen
2013-02-26 20:54 ` Eric W. Biederman
2013-03-04 5:25 ` Jonathan Woithe
2013-02-20 5:50 ` Simon Jeons
2013-02-20 7:05 ` David Rientjes [this message]
2013-03-16 9:25 Hillf Danton
2013-03-16 9:33 ` Raymond Jennings
2013-03-16 11:02 ` Jonathan Woithe
2013-03-20 5:47 ` Jonathan Woithe
2013-03-21 7:07 ` Jonathan Woithe
2013-03-25 2:24 ` Jonathan Woithe
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=alpine.DEB.2.02.1302192302270.27407@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=jwoithe@atrad.com.au \
--cc=linux-mm@kvack.org \
--cc=simon.jeons@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