mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@freenet.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23-pre VM regression?
Date: Fri, 17 Oct 2003 01:37:49 +0200	[thread overview]
Message-ID: <bmna4e$4bi$1@ID-44327.news.dfncis.de> (raw)
In-Reply-To: <fa.j3l9liv.1djudhj@ifi.uio.no>

Tvrtko A. Uršulin wrote:

> 
>> So a lot of processes which should not get killed are dying. This is
>> really bad. I was afraid it could happen and it did.
>>
>> What now? Resurrect OOM-killer?
> 
> Regards to all,
> 
> It seems that this topic is very persistent. I have RFC-ed this patch
> (attached) a few days and here it goes again.
> 
> It makes OOM Killer a compile time option (IMHO better than completely
> remove or fixed-include it). Even, more, it makes it completely modular
> and adds two new killers.
> 
> Any comments?

I think it would be good to have it as option. Maybe there are situations,
where the old model is better then the new one.

But let me say, that the OOM Killer has its problems too: I often saw
servers with killed sshd or apache, named, ... instead of the bad
rsync-process, which eats up all the memory ressources until the OOM killer
killed it.

Onother thing:
the new VM is the best VM I ever saw in a 2.4.x kernel. On the desktop with
512 MB RAM and used 230MB swap and 14MB/s HD i/o (IDE) and KDE compiling
(load about 3), I was able to look mpeg's without any problem.


Kind regards,
Andreas Hartmann

       reply	other threads:[~2003-10-16 23:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.jkt135h.1l0s0t@ifi.uio.no>
     [not found] ` <fa.j3l9liv.1djudhj@ifi.uio.no>
2003-10-16 23:37   ` Andreas Hartmann [this message]
2003-10-18 22:09 A.D.F.
  -- strict thread matches above, loose matches on Subject: below --
2003-10-16 11:52 Marcelo Tosatti
2003-10-16 13:15 ` Tvrtko A. Uršulin
2003-10-16 13:24 ` Andrea Arcangeli
2003-10-16 12:29   ` Marcelo Tosatti
2003-10-16 13:35     ` Andrea Arcangeli
2003-10-19 23:21       ` Ken Moffat
2003-10-21  9:25         ` Stephan von Krawczynski
2003-10-27 21:11           ` Mike Fedyk

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='bmna4e$4bi$1@ID-44327.news.dfncis.de' \
    --to=andihartmann@freenet.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome