public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Enabling other oom schemes
Date: Sun, 14 Sep 2003 00:04:01 +0200	[thread overview]
Message-ID: <20030913220401.GA17528@hh.idb.hist.no> (raw)
In-Reply-To: <1063476152.24473.30.camel@localhost>

On Sat, Sep 13, 2003 at 04:52:56PM -0400, Robert Love wrote:
> On Sat, 2003-09-13 at 13:48, Jamie Lokier wrote:
> 
> > Also, when the OOM condition is triggered I'd like the system to
> > reboot, but first try for a short while to unmount filesystems cleanly.
> > 
> > Any chance of those things?
> 
> I like all of these ideas.
> 
> One thing to keep in mind is that during a real OOM condition, we cannot
> allocate _any_ memory.  None. Zilch.
> 
So a "complicated" oom handler need to preallocate all the memory
it might ever need.  Not impossible.

Helge Hafting

  reply	other threads:[~2003-09-13 21:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12  2:19 [RFC] Enabling other oom schemes Rusty Lynch
2003-09-12  4:18 ` Rahul Karnik
2003-09-12  4:31   ` Chris Friesen
2003-09-12  4:40     ` Rahul Karnik
2003-09-12  4:48       ` Robert Love
2003-09-12 11:18     ` Helge Hafting
2003-09-12 14:07       ` Chris Friesen
2003-09-12  4:47   ` Robert Love
2003-09-12  4:50 ` Robert Love
2003-09-12 10:42   ` Alan Cox
2003-09-12  8:58 ` Tvrtko A. Uršulin
2003-09-13  2:21   ` Rusty Lynch
2003-09-15 10:59     ` Tvrtko A. Uršulin
2003-09-13 17:48 ` Jamie Lokier
2003-09-13 20:52   ` Robert Love
2003-09-13 22:04     ` Helge Hafting [this message]
2003-09-14  0:55       ` Robert Love
2003-09-14  9:12         ` Helge Hafting
2003-09-14  5:28     ` Chris Friesen
2003-09-15  0:11     ` Mike S

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=20030913220401.GA17528@hh.idb.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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