From: Robert Love <rml@tech9.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: rusty@linux.co.intel.com, riel@conectiva.com.br,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Enabling other oom schemes
Date: Sat, 13 Sep 2003 16:52:56 -0400 [thread overview]
Message-ID: <1063476152.24473.30.camel@localhost> (raw)
In-Reply-To: <20030913174825.GB7404@mail.jlokier.co.uk>
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.
And that makes some things very hard. When we start getting into things
such as complicated policies that kill nonessential services first, et
cetera... there comes a time where a lot of communication is needed
(probably with user-space). Hard to do that with no memory.
I do like all of this, however, and want to see some different OOM
killers.
Robert Love
WARNING: multiple messages have this Message-ID (diff)
From: Robert Love <rml@tech9.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: rusty@linux.co.intel.com, riel@conectiva.com.br,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Enabling other oom schemes
Date: Sat, 13 Sep 2003 16:52:56 -0400 [thread overview]
Message-ID: <1063476152.24473.30.camel@localhost> (raw)
In-Reply-To: <20030913174825.GB7404@mail.jlokier.co.uk>
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.
And that makes some things very hard. When we start getting into things
such as complicated policies that kill nonessential services first, et
cetera... there comes a time where a lot of communication is needed
(probably with user-space). Hard to do that with no memory.
I do like all of this, however, and want to see some different OOM
killers.
Robert Love
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-09-13 20:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 2:19 [RFC] Enabling other oom schemes Rusty Lynch
2003-09-12 2:19 ` Rusty Lynch
2003-09-12 4:18 ` Rahul Karnik
2003-09-12 4:18 ` Rahul Karnik
2003-09-12 4:31 ` Chris Friesen
2003-09-12 4:31 ` Chris Friesen
2003-09-12 4:40 ` Rahul Karnik
2003-09-12 4:40 ` Rahul Karnik
2003-09-12 4:48 ` Robert Love
2003-09-12 4:48 ` Robert Love
2003-09-12 11:18 ` Helge Hafting
2003-09-12 11:18 ` Helge Hafting
2003-09-12 14:07 ` Chris Friesen
2003-09-12 14:07 ` Chris Friesen
2003-09-12 14:30 ` M. Edward Borasky
2003-09-12 4:47 ` Robert Love
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 17:48 ` Jamie Lokier
2003-09-13 20:52 ` Robert Love [this message]
2003-09-13 20:52 ` Robert Love
2003-09-13 22:04 ` Helge Hafting
2003-09-14 0:55 ` Robert Love
2003-09-14 9:12 ` Helge Hafting
2003-09-14 5:28 ` Chris Friesen
2003-09-14 5:28 ` Chris Friesen
2003-09-15 0:11 ` Mike S
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=1063476152.24473.30.camel@localhost \
--to=rml@tech9.net \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=rusty@linux.co.intel.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 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.