From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Andrea Arcangeli <aarcange@redhat.com>,
vedran.furac@gmail.com,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [PATCH] oom_kill: use rss value instead of vm size for badness
Date: Thu, 29 Oct 2009 18:16:50 +0900 [thread overview]
Message-ID: <20091029181650.979bf95c.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0910290156560.16347@chino.kir.corp.google.com>
On Thu, 29 Oct 2009 02:01:49 -0700 (PDT)
David Rientjes <rientjes@google.com> wrote:
> > yes, then I wrote "as start point". There are many environments.
>
> And this environment has a particularly bad result.
> yes, then I wrote "as start point". There are many environments.
In my understanding, 2nd, 3rd candidates are not important. If both of
total_vm and RSS catches the same process as 1st candidate, it's ok.
(i.e. If killed, oom situation will go away.)
> > ya, I'm now considering to drop file_rss from calculation.
> >
> > some reasons.
> >
> > - file caches remaining in memory at OOM tend to have some trouble to remove it.
> > - file caches tend to be shared.
> > - if file caches are from shmem, we never be able to drop them if no swap/swapfull.
> >
> > Maybe we'll have better result.
> >
>
> That sounds more appropriate.
>
> I'm surprised you still don't see a value in using the peak VM and RSS
> sizes, though, as part of your formula as it would indicate the proportion
> of memory resident in RAM at the time of oom.
>
I'll use swap_usage instead of peak VM size as bonus.
anon_rss + swap_usage/2 ? or some.
My first purpose is not to kill not-guilty process at random.
If memory eater is killed, it's reasnoable.
In my consideration
- "Killing a process because of OOM" is something bad, but not avoidable.
- We don't need to do compliated/too-wise calculation for killing a process.
"The worst one is memory-eater!" is easy to understand to users and admins.
- We have oom_adj, now. User can customize it if he run _important_ memory eater.
- But fork-bomb doesn't seem memory eater if we see each process.
We need some cares.
Then,
- I'd like to drop file_rss.
- I'd like to take swap_usage into acccount.
- I'd like to remove cpu_time bonus. runtime bonus is much more important.
- I'd like to remove penalty from children. To do that, fork-bomb detector
is necessary.
- nice bonus is bad. (We have oom_adj instead of this.) It should be
if (task_nice(p) < 0)
points /= 2;
But we have "root user" bonus already. We can remove this line.
After above, much more simple selection, easy-to-understand, will be done.
Thanks,
-Kame
--
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:[~2009-10-29 9:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 8:58 KAMEZAWA Hiroyuki
2009-10-28 9:15 ` David Rientjes
2009-10-28 11:04 ` KAMEZAWA Hiroyuki
2009-10-29 1:00 ` KAMEZAWA Hiroyuki
2009-10-29 2:31 ` Minchan Kim
2009-10-29 8:31 ` David Rientjes
2009-10-29 8:46 ` KAMEZAWA Hiroyuki
2009-10-29 9:01 ` David Rientjes
2009-10-29 9:16 ` KAMEZAWA Hiroyuki [this message]
2009-10-29 9:44 ` David Rientjes
2009-10-29 23:41 ` KAMEZAWA Hiroyuki
2009-11-01 13:29 ` KOSAKI Motohiro
2009-11-02 10:42 ` David Rientjes
2009-11-02 12:35 ` KOSAKI Motohiro
2009-11-02 19:55 ` Vedran Furač
2009-11-03 23:09 ` KOSAKI Motohiro
2009-11-07 19:16 ` Vedran Furač
2009-11-25 12:44 ` Andrea Arcangeli
2009-11-25 21:39 ` David Rientjes
2009-11-27 18:26 ` Andrea Arcangeli
2009-11-30 23:09 ` David Rientjes
2009-12-01 4:43 ` KOSAKI Motohiro
2009-12-01 22:20 ` David Rientjes
2009-12-02 0:35 ` KOSAKI Motohiro
2009-12-03 23:25 ` David Rientjes
2009-12-04 0:44 ` KAMEZAWA Hiroyuki
2009-11-26 0:10 ` Vedran Furač
2009-11-26 1:32 ` KAMEZAWA Hiroyuki
2009-11-27 1:56 ` Vedran Furač
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=20091029181650.979bf95c.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=vedran.furac@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