From: Giuliano Pochini <pochini@shiny.it>
To: Jim Sibley <jlsibley@us.ibm.com>
Cc: Troy Reed <tdreed@us.ibm.com>,
ltc@linux.ibm.com, riel@conectiva.com.br,
linux-kernel@vger.kernel.org
Subject: RE: Killing/balancing processes when overcommited
Date: Thu, 12 Sep 2002 09:25:26 +0200 (CEST) [thread overview]
Message-ID: <XFMail.20020912092526.pochini@shiny.it> (raw)
In-Reply-To: <OFA28F240F.93209971-ON88256C31.005E5F03@boulder.ibm.com>
On 11-Sep-2002 Jim Sibley wrote:
> I have run into a situation in a multi-user Linux environment that when
> memory is exhausted, random things happen. [...] In a "well tuned" system,
> we are safe, but when the system accidentally (or deliberately) becomes
> "detuned", oom_kill is entered and arbitrarily kills a process.
It's not difficult to make the kerner choose the right processes
to kill. It's impossible. Imagine that when it goes oom the system
stops and asks you what processes have to be killed. What do you
kill ? I think the only way to save the system it to tell the kernel
which are the processes that must not be killed, except in extreme
conditions. Probably we do need an oomd that the sysadmin can
configure as he likes.
Bye.
next prev parent reply other threads:[~2002-09-12 7:20 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 18:08 Killing/balancing processes when overcommited Jim Sibley
2002-09-11 18:27 ` Jurriaan
2002-09-12 8:26 ` Helge Hafting
2002-09-11 21:44 ` Alan Cox
2002-09-12 7:06 ` Tim Connors
2002-09-12 7:25 ` Giuliano Pochini [this message]
2002-09-12 16:02 ` Rik van Riel
2002-09-12 18:30 ` Thunder from the hill
2002-09-13 8:17 ` Giuliano Pochini
2002-09-13 10:22 ` Thunder from the hill
2002-09-13 12:53 ` Denis Vlasenko
2002-09-13 12:54 ` Jesse Pollard
2002-09-12 18:14 Jim Sibley
2002-09-12 19:00 Jim Sibley
2002-09-12 19:08 ` Thunder from the hill
2002-09-12 20:35 ` Alan Cox
2002-09-12 20:43 ` Thunder from the hill
2002-09-12 20:55 ` Alan Cox
2002-09-12 21:15 ` Thunder from the hill
2002-09-12 21:22 ` Jesse Pollard
2002-09-12 23:08 ` Alan Cox
2002-09-12 23:12 ` Thunder from the hill
2002-09-12 21:19 ` Jesse Pollard
2002-09-12 21:56 ` Thunder from the hill
2002-09-13 7:51 ` Giuliano Pochini
2002-09-13 10:17 ` Thunder from the hill
2002-09-12 19:09 ` Rik van Riel
2002-09-13 8:05 ` Giuliano Pochini
2002-09-13 10:54 ` Helge Hafting
2002-09-13 13:02 ` Giuliano Pochini
2002-09-13 16:40 ` Gerhard Mack
2002-09-13 20:23 ` Timothy D. Witham
2002-09-13 21:13 Jim Sibley
2002-09-13 22:31 ` Timothy D. Witham
2002-09-13 22:38 ` Timothy D. Witham
2002-09-13 22:44 ` Rik van Riel
2002-09-13 23:12 ` Timothy D. Witham
2002-09-16 7:29 ` Helge Hafting
2002-09-16 14:03 ` Rik van Riel
2002-09-16 18:49 ` Timothy D. Witham
2002-09-16 19:11 ` Rik van Riel
2002-09-16 20:27 ` Timothy D. Witham
2002-09-14 0:23 ` Jim Sibley
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=XFMail.20020912092526.pochini@shiny.it \
--to=pochini@shiny.it \
--cc=jlsibley@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltc@linux.ibm.com \
--cc=riel@conectiva.com.br \
--cc=tdreed@us.ibm.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;
as well as URLs for NNTP newsgroup(s).