linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Peter Bergmann" <bergmann.peter@gmx.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org, kristian.peters@korseby.net,
	nfedera@esesix.at, andrea@suse.de, riel@redhat.com
Subject: Re: Configurable OOM killer Re: old oom-vm for 2.4.32 (was oom killer in 2.4.23)
Date: Mon, 8 Dec 2003 23:00:55 +0100 (MET)	[thread overview]
Message-ID: <26836.1070920855@www56.gmx.net> (raw)
In-Reply-To: Pine.LNX.4.44.0312081512510.1289-100000@logos.cnet


> On Sat, 6 Dec 2003, Peter Bergmann wrote:
> 
> > > > If anyone  is interested:
> > > > Norbert Federa sent me this link for a "quick&dirty" patch he made 
> > > > for 2.4.23-vanilla which rolls back the complete 2.4.22 vm including
> the
> > > > old oom-killer  - without guarantee but it does work very well for
> me
> > > ...
> > > 
> > > I suppose the oom killer is the only reason for you using .22 VM
> correct?
> > > 
> > > Or do you have any other reason for this?
> > 
> > No, you're right. The oom killer is the _only_reason. 
> > I did not succeed in integrating the disabled oom_kill.c in 2.4.23.
> > The only solution for me is applying Norbert's .22vm patch.
> 
> Hi,
> 
> The following patch makes OOM killer configurable (its the same as the 
> other patches posted except its around CONFIG_OOM_KILLER).
> 
> I hope the Configure.help entry is clear enough.
> 
> Peter, can you please try this.
> 
> Comments are appreciated.

Great. seems to work very well. Thx.
Ran some very hungry testprogs (memeat.c), filled a tmpfs with crap, ... 
I was satisfied with oom's kill decisions.
And it is/was very easy to modify/extend oom_kill.c  for special needs.

Maybe the Configure.help text should be somewhat more frightening.
I think aa had good reasons for disabling oom (possibility of lock up) but
among others 
I'd prefer to see your patch - a config option (default disabled +
experimental)  - in 2.4.24.

Cheers,
Pet

-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net



  reply	other threads:[~2003-12-08 22:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05 15:03 old oom-vm for 2.4.32 (was oom killer in 2.4.23) Peter Bergmann
2003-12-05 19:02 ` Marcelo Tosatti
2003-12-05 23:08   ` Peter Bergmann
2003-12-08 17:15     ` Configurable OOM killer " Marcelo Tosatti
2003-12-08 22:00       ` Peter Bergmann [this message]
2003-12-15 22:28       ` Ernie Petrides
2003-12-16  0:48         ` Marcelo Tosatti
     [not found] <Zxp0-1lf-9@gated-at.bofh.it>
     [not found] ` <10xwC-2O0-7@gated-at.bofh.it>
2003-12-09 18:34   ` Kristian Peters
2003-12-16 13:08     ` Marcelo Tosatti

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=26836.1070920855@www56.gmx.net \
    --to=bergmann.peter@gmx.net \
    --cc=andrea@suse.de \
    --cc=kristian.peters@korseby.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=nfedera@esesix.at \
    --cc=riel@redhat.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).