From: David Chinner <dgc@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>, linux-mm@kvack.org
Subject: Re: [RFC] [PATCH] support for oom_die
Date: Wed, 12 Apr 2006 10:37:12 +1000 [thread overview]
Message-ID: <20060412003712.GB2732@melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604111025110.564@schroedinger.engr.sgi.com>
On Tue, Apr 11, 2006 at 10:28:32AM -0700, Christoph Lameter wrote:
> On Tue, 11 Apr 2006, KAMEZAWA Hiroyuki wrote:
>
> > I think 2.6 kernel is very robust against OOM situation but sometimes
> > it occurs. Yes, oom_kill works enough and exit oom situation, *when*
> > the system wants to survive.
>
> A user process can cause an oops by using too much memory? Would it not be
> better to terminate the rogue process instead? Otherwise any user can
> bring down the system?
In a HA environment, the OOM killer can take out the failover daemon
or other services and the failover infrastructure may not be able to
handle this gracefully and services will become unavailable. This is
about the worst thing that can happen in this environment.
In these situations, it is better to panic the box on OOM and get a
clean failover of services than risk having the OOM killer
compromise your HA setup.
Also, you typically don't have Random J. User logging in and running
stuff on HA server clusters, so if you're in an OOM situation there
is already something wrong that needs fixing.....
Cheers,
Dave.
--
Dave Chinner
R&D Software Enginner
SGI Australian Software Group
--
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:[~2006-04-12 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 5:29 KAMEZAWA Hiroyuki
2006-04-11 17:28 ` Christoph Lameter
2006-04-11 17:39 ` Om Narasimhan
2006-04-12 0:37 ` David Chinner [this message]
2006-04-12 1:11 ` KAMEZAWA Hiroyuki
2006-04-12 3:31 ` Rik van Riel
2006-04-12 4:49 ` KAMEZAWA Hiroyuki
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=20060412003712.GB2732@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
/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