All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jonmasters@gmail.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] oom_pardon, aka don't kill my xlock
Date: Fri, 24 Sep 2004 23:57:40 +0100	[thread overview]
Message-ID: <35fb2e5904092415572e58ee66@mail.gmail.com> (raw)
In-Reply-To: <20040923234520.GA7303@pclin040.win.tue.nl>

On Fri, 24 Sep 2004 01:45:20 +0200, Andries Brouwer <aebr@win.tue.nl> wrote:

> On Thu, Sep 23, 2004 at 01:23:08AM +0200, Thomas Habets wrote:

> > How about a sysctl that does "for the love of kbaek, don't ever kill these
> > processes when OOM. If nothing else can be killed, I'd rather you panic"?

> An aircraft company discovered that it was cheaper to fly its planes
> with less fuel on board. The planes would be lighter and use less fuel
> and money was saved. On rare occasions however the amount of fuel was
> insufficient, and the plane would crash. This problem was solved by
> the engineers of the company by the development of a special OOF
> (out-of-fuel) mechanism.

For the curious I have recently been reading about this (I'm a nervous
flyer, you wouldn't believe the kind of statistics I scare myself
with) and discovered the term RAT - RAM Air Turbine. In the event of
fuel running out, modern aircraft automatically drop this turbine and
generate sufficient power for navigation (and hopefully safe landing).
There's a famous early 1980s case in Canada known as the Gimli Glider
in which this actually ended up happing after a computer that
performed imperial/metric conversion failed and the manual calculation
was wrong - they coined a popular Canadian phrase because of this.

What we need is a mechanism to have a giant brainstraw emerge from the
front casing of the machine and suck the brains out of the guy running
a server with overcommit issues.

[ Alan has a working model super drinking straw from OLS - pity you
destroyed it. ]

Jon.

  parent reply	other threads:[~2004-09-24 22:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 23:23 [PATCH] oom_pardon, aka don't kill my xlock Thomas Habets
2004-09-23  0:01 ` Nick Piggin
2004-09-23  0:07 ` William Lee Irwin III
2004-09-23  4:45 ` Tonnerre
2004-09-23  6:57   ` Thomas Habets
2004-09-23 12:24     ` Tonnerre
2004-09-23 13:32       ` Thomas Habets
2004-09-23 23:45 ` Andries Brouwer
2004-09-24 13:19   ` Alan Cox
2004-09-24 19:58     ` Thomas Habets
2004-09-24 21:15       ` Alan Cox
2004-09-25 10:08         ` Thomas Habets
2004-09-27 10:41         ` Marcelo Tosatti
2004-09-27 12:54           ` Lars Marowsky-Bree
2004-09-27 13:12             ` Jon Masters
2004-09-27 12:36               ` Alan Cox
2004-09-27 13:35               ` Marcelo Tosatti
2004-09-27 15:59                 ` Jon Masters
2004-09-27 17:12                 ` Herbert Poetzl
2004-09-27 16:42                   ` Marcelo Tosatti
2004-09-28 13:33                     ` Herbert Poetzl
2004-09-28 12:32                       ` Marcelo Tosatti
2004-09-28 23:55                         ` Herbert Poetzl
2004-09-27 23:07                   ` Jon Masters
2004-09-29  0:49           ` Andries Brouwer
2004-09-24 14:07   ` Pavel Machek
2004-09-24 22:57   ` Jon Masters [this message]
2004-09-25 16:32 ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2004-09-27 12:00 Thomas Habets
2004-09-27 12:17 ` Jon Masters

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=35fb2e5904092415572e58ee66@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --cc=aebr@win.tue.nl \
    --cc=jonathan@jonmasters.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.