From: Guest section DW <dwguest@win.tue.nl>
To: Sean Hunter <sean-lk@dev.sportingbet.com>, linux-kernel@vger.kernel.org
Subject: Re: OOM killer???
Date: Thu, 29 Mar 2001 14:57:12 +0200 [thread overview]
Message-ID: <20010329145712.A8739@win.tue.nl> (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> <20010329130238.G10301@dev.sportingbet.com>
In-Reply-To: <20010329130238.G10301@dev.sportingbet.com>; from Sean Hunter on Thu, Mar 29, 2001 at 01:02:38PM +0100
On Thu, Mar 29, 2001 at 01:02:38PM +0100, Sean Hunter wrote:
> 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.
Yes. But today Linux willing overcommits. It would be better if
the default was not to.
> 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_.
Unix V6 did not overcommit, and panicked if is was out of swap
because that was a cannot happen situation.
If you argue that we must design things so that there is no overcommit
and still have an OOM killer just in case, I have no objections at all.
next prev parent reply other threads:[~2001-03-29 12:58 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
2001-03-29 12:57 ` Guest section DW [this message]
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=20010329145712.A8739@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sean-lk@dev.sportingbet.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