From: Sean Hunter <sean-lk@dev.sportingbet.com>
To: Guest section DW <dwguest@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM killer???
Date: Thu, 29 Mar 2001 13:02:38 +0100 [thread overview]
Message-ID: <20010329130238.G10301@dev.sportingbet.com> (raw)
In-Reply-To: <200103282138.f2SLcT824292@webber.adilger.int> <Pine.A32.3.95.1010329111147.63156A-100000@werner.exp-math.uni-essen.de> <20010329130154.A8701@win.tue.nl>
In-Reply-To: <20010329130154.A8701@win.tue.nl>; from dwguest@win.tue.nl on Thu, Mar 29, 2001 at 01:01:54PM +0200
On Thu, Mar 29, 2001 at 01:01:54PM +0200, Guest section DW wrote:
> [Never use planes where the company's engineers spend their
> time designing algorithms for selecting which passenger
> must be thrown out when the plane is overloaded.]
This is (as far as I can see) a fantastically specious argument. A plane is
designed to function in an entirely constrained mode of operation and in an
entirely well-understood and circumscribed problem space, whereas a linux host
is a general-purpose device which can be used for many different applications.
The reason the aero engineers don't need to select a passanger to throw out
when the plane is overloaded is simply that the plane operators do not allow
the plane to become overloaded. If I put a 100 people in a trilander it may
take off, but won't fly, and will probably crash. The plane's designers don't
have to do anything about that- we do.
Furthermore, why do you suppose an aeroplane has more than one altimeter,
artifical horizon and compass? Do you think it's because they are unable to
make one of each that is reliable? Or do you think its because they are
concerned about what happens if one fails _however unlikely that is_.
In fact, aeroplane engineers do design in ways of mitigating the effects of all
kinds of failures, including lessening the impact of a crash (directly
analogous to our OOM killer). For example, they provide means of jettisonning
fuel prior to crash landing to attempt to minimise explosions.
Risk management is about lessening impact as well as lessening probability. If
something is important, you don't only make it work as well as you can, you
mitigate the effect of failure. A reliable system is not just a strong belt,
it is belt, braces, suspenders and bicycle clips.
I have seen the OOM killer in operation three times on our production servers.
In each case it kept the machine alive in the face of hostile runaway
processes. I don't want to see things killed, but if that is the only way to
keep the host alive, I vote to keep it alive.
When I'm on a plane, I want more than one engine _and_ lifejackets.
Sean
next prev parent reply other threads:[~2001-03-29 12:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200103282138.f2SLcT824292@webber.adilger.int>
2001-03-29 9:29 ` OOM killer??? Dr. Michael Weller
2001-03-29 11:01 ` Guest section DW
2001-03-29 12:02 ` Sean Hunter [this message]
2001-03-29 12:57 ` Guest section DW
2001-03-29 15:41 ` David Konerding
2001-03-29 17:52 ` David Lang
2001-03-30 2:26 ` Michael Peddemors
2001-03-30 14:48 ` J. Scott Kasten
2001-03-29 17:21 ` Stephen Satchell
2001-03-29 13:53 ` Szabolcs Szakacsits
2001-03-29 15:01 ` Dr. Michael Weller
2001-03-29 16:29 ` Szabolcs Szakacsits
2001-03-29 16:51 ` Szabolcs Szakacsits
2001-03-29 19:20 Jesse Pollard
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 16:22 Jesse Pollard
2001-03-27 10:59 Rogier Wolff
2001-03-27 12:14 ` Jonathan Morton
2001-03-27 13:24 ` Martin Dalecki
2001-03-27 15:31 ` Jonathan Lundell
2001-03-27 18:08 ` Ingo Oeser
2001-03-27 19:07 ` Martin Dalecki
2001-03-27 19:55 ` Andreas Dilger
2001-03-27 21:13 ` Andreas Rogge
2001-03-27 18:37 ` Jonathan Morton
2001-03-27 13:57 ` Jonathan Morton
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=20010329130238.G10301@dev.sportingbet.com \
--to=sean-lk@dev.sportingbet.com \
--cc=dwguest@win.tue.nl \
--cc=linux-kernel@vger.kernel.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