From: David Rientjes <rientjes@google.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Paul Menage <menage@google.com>, Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>, Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH] copy over oom_adj value at fork time
Date: Mon, 27 Jul 2009 23:14:12 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0907272311370.26430@chino.kir.corp.google.com> (raw)
In-Reply-To: <20090728120822.D80C.A69D9226@jp.fujitsu.com>
On Tue, 28 Jul 2009, KOSAKI Motohiro wrote:
> Actually, if we assume the administrator is really stupid, he can mark
> all processes as OOM_DISABLE. it makes livelock anyway.
Wrong, the oom killer will panic the machine if there are no eligible
tasks to kill. That's actually a more desirable result in most
circumstances over livelocking.
> ITOH, we never seen this livelock on vfork()ed application.
>
I have, which is why I wrote my patches.
> More important thing is: Documentation/filesysmtem/proc/txt says
> oom_adj is process property and vfork()ed parent and child are definitelly
> another process.
>
I've proposed adding /proc/pid/oom_adj_child so that newly initialized
mm's start with a default oom_adj value. Paul suggested that it be a
per-task characteristic, so that's what I'm looking at implementing.
Thanks.
next prev parent reply other threads:[~2009-07-28 6:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906020557.n525v6KO004302@imap1.linux-foundation.org>
2009-07-15 0:52 ` + oom-move-oom_adj-value-from-task_struct-to-mm_struct.patch added to -mm tree Paul Menage
2009-07-15 1:05 ` [PATCH] copy over oom_adj value at fork time Rik van Riel
2009-07-15 1:15 ` Paul Menage
2009-07-15 2:01 ` KOSAKI Motohiro
2009-07-15 2:12 ` [PATCH -mm] copy over oom_adj value at fork time (v2) Rik van Riel
2009-07-15 3:42 ` David Rientjes
2009-07-15 3:48 ` [PATCH] copy over oom_adj value at fork time David Rientjes
2009-07-16 23:29 ` Paul Menage
2009-07-17 9:34 ` David Rientjes
2009-07-17 20:03 ` Paul Menage
2009-07-17 23:12 ` David Rientjes
2009-07-20 21:52 ` Paul Menage
2009-07-21 3:40 ` David Rientjes
2009-07-21 7:19 ` KOSAKI Motohiro
2009-07-21 16:06 ` Paul Menage
2009-07-21 19:54 ` David Rientjes
2009-07-21 19:57 ` Paul Menage
2009-07-21 20:00 ` David Rientjes
2009-07-21 20:03 ` Paul Menage
2009-07-23 23:21 ` KOSAKI Motohiro
2009-07-23 23:29 ` David Rientjes
2009-07-24 1:10 ` KOSAKI Motohiro
2009-07-24 9:27 ` David Rientjes
2009-07-28 6:09 ` KOSAKI Motohiro
2009-07-28 6:14 ` David Rientjes [this message]
2009-07-15 1:49 ` 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=alpine.DEB.2.00.0907272311370.26430@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=menage@google.com \
--cc=npiggin@suse.de \
--cc=riel@redhat.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
all inboxes | Powered by JetHome®