From: safemode <safemode@speakeasy.net>
To: Rik van Riel <riel@conectiva.com.br>, "H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: VM nuisance
Date: Sat, 11 Aug 2001 00:41:12 -0400 [thread overview]
Message-ID: <20010811044103Z270717-760+22@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108110117160.3530-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0108110117160.3530-100000@imladris.rielhome.conectiva>
On Saturday 11 August 2001 00:17, Rik van Riel wrote:
> On 10 Aug 2001, H. Peter Anvin wrote:
> > > I haven't got the faintest idea how to come up with an OOM
> > > killer which does the right thing for everybody.
> >
> > Basically because there is no such thing?
>
> Actually the killer itself isn't the problem.
>
> It's deciding when to let it kick in.
I was under the presumption from what David and others have said that the OOM
sometimes works the way it was meant to and kills the offending program, or
it put the box into this super sluggish state for a very long time regardless
if it was early or late. If it only happens when it's late then what was
David talking about?
> Rik
> --
> IA64: a worthy successor to i860.
>
> http://www.surriel.com/ http://distro.conectiva.com/
>
> Send all your spam to aardvark@nl.linux.org (spam digging piggy)
>
next prev parent reply other threads:[~2001-08-11 4:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 1:30 VM nuisance David Ford
2001-08-11 2:48 ` Rik van Riel
2001-08-11 2:59 ` H. Peter Anvin
2001-08-11 4:17 ` Rik van Riel
2001-08-11 4:40 ` David Ford
2001-08-11 4:46 ` Rik van Riel
2001-08-11 4:41 ` safemode [this message]
2001-08-11 5:00 ` H. Peter Anvin
2001-08-11 13:13 ` Alan Cox
2001-08-11 15:39 ` David Ford
2001-08-11 3:50 ` safemode
2001-08-12 13:09 ` Maciej Zenczykowski
2001-08-12 13:45 ` Rik van Riel
2001-08-16 23:29 ` Justin A
2001-08-17 0:06 ` Dr. Kelsey Hudson
2001-08-17 0:24 ` Justin A
2001-08-17 2:54 ` Dr. Kelsey Hudson
2001-08-12 23:05 ` Dan Mann
[not found] ` <9l5v9a$ha9$1@ns1.clouddancer.com>
2001-08-13 0:01 ` Colonel
2001-08-13 14:32 ` dean gaudet
2001-08-13 19:47 ` Brian
2001-08-14 8:27 ` Helge Hafting
2001-08-17 13:34 ` Szabolcs Szakacsits
2001-08-17 17:29 ` Rik van Riel
2001-08-14 14:00 ` "VM watchdog"? [was Re: VM nuisance] Pavel Machek
2001-08-16 22:24 ` Jakob Østergaard
2001-08-17 1:26 ` David Ford
2001-08-17 1:41 ` Jakob Østergaard
[not found] ` <9li6sf$h5$1@ns1.clouddancer.com>
2001-08-17 9:04 ` Colonel
2001-08-17 20:38 ` David Ford
[not found] <20010811035112.59EC438D01@perninha.conectiva.com.br>
2001-08-11 3:52 ` VM nuisance Rik van Riel
[not found] <no.id>
2001-08-11 16:45 ` Alan Cox
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=20010811044103Z270717-760+22@vger.kernel.org \
--to=safemode@speakeasy.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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