From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Mikael Starvik <mikael.starvik@axis.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Cc: Jonas Holmberg <jonas.holmberg@axis.com>,
Sebastian Sjoberg <sebastian.sjoberg@axis.com>
Subject: Re: oom killer and its superior braindamage in 2.4
Date: Mon, 24 Feb 2003 10:27:51 +0100 [thread overview]
Message-ID: <200302241026.11321.m.c.p@wolk-project.de> (raw)
In-Reply-To: <3C6BEE8B5E1BAC42905A93F13004E8AB017DE83A@mailse01.axis.se>
On Monday 24 February 2003 10:13, Mikael Starvik wrote:
Hi Mikael,
> Does everyone agree that killing a process is always the best approach
> to resolve an OOM? If the OOM is caused by e.g. a growing tmpfs or
> memory leaks in the kernel it won't help much to kill processes that
> may respawn.
Well, I don't agree that it's always the best approach. Other bad things, you
metioned it, can happen.
> Would it be useful if it was possible to register another oom-handler?
> Some architectures could then choose to e.g. reboot the system instead.
I'd like to see _an option_ (read: not default but an option, e.g. boot
parameter) that will reboot the machine after $specified_time if an OOM
killing action does not stop.
ciao, Marc
next prev parent reply other threads:[~2003-02-24 9:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 9:13 Mikael Starvik
2003-02-24 9:27 ` Marc-Christian Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-23 16:06 David Mansfield
2003-02-23 16:25 ` Faik Uygur
2003-02-23 16:25 ` Rik van Riel
2003-02-23 18:07 ` David Mansfield
2003-02-23 20:14 ` Rik van Riel
2003-02-23 20:22 ` David Mansfield
2003-02-23 20:53 ` Rik van Riel
2003-02-22 19:35 Marc-Christian Petersen
2003-02-22 20:14 ` Rik van Riel
2003-02-22 20:32 ` Rik van Riel
2003-02-23 17:35 ` Marc-Christian Petersen
2003-02-23 20:18 ` Rik van Riel
2003-02-23 20:29 ` Marc-Christian Petersen
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=200302241026.11321.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=jonas.holmberg@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.com \
--cc=sebastian.sjoberg@axis.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
all inboxes | Powered by JetHome®