public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Yann Dirson <ydirson@altern.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: Looking for better 2.2-based VM (do_try_to_free_pages fails, machine hangs)
Date: Fri, 3 Nov 2000 16:24:09 +0100	[thread overview]
Message-ID: <20001103162409.S7204@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20001101174816.A18510@athlon.random> <Pine.LNX.4.21.0011011456430.11112-100000@duckman.distro.conectiva> <20001101220326.A4514@bylbo.nowhere.earth>
In-Reply-To: <20001101220326.A4514@bylbo.nowhere.earth>; from ydirson@altern.org on Wed, Nov 01, 2000 at 10:03:27PM +0100

On Wed, Nov 01, 2000 at 10:03:27PM +0100, Yann Dirson wrote:
> On Wed, Nov 01, 2000 at 02:59:01PM -0200, Rik van Riel wrote:
> > it appears there has been amazingly little research on this
> > subject and it's completely unknown which approach will work
> > "best" ... or even, what kind of behaviour is considered to
> > be best by the users...
> 
> Sounds to me like a good point to favour a config-time selection of
> OOM killers.

Better yet: Apply my OOM-Killer-API-Patch[1] and build your own
OOM-Killer!

Just lock your module into memory, supply an function to
install_oom_killer(), save the old one (you get it as return if
installing it went ok) and be happy.

And now have fun bringing your machine into OOM situations.

Want to change it back? No problem. Just get signaled somehow[2],
reinstall the old one, unlock your module and wait to be cleaned
up.

I never tried it above Riks 2.2.x-OOM-Killer-Patch, but it should
work on top of it, because oom_kill.c isn't all that different.

Regards

Ingo Oeser

[1] http://www.tu-chemnitz.de/~ioe/oom_kill_api.patch
[2] if you don't know that much about the kernel, you shouldn't
   play with oom-handlers anyway ;-)
-- 
Feel the power of the penguin - run linux@your.pc
<esc>:x
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-03 15:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-01 12:33 Looking for better 2.2-based VM (do_try_to_free_pages fails, machine hangs) Yann Dirson
2000-11-01 11:41 ` Marcelo Tosatti
2000-11-01 16:43   ` Yann Dirson
2000-11-01 16:48     ` Andrea Arcangeli
2000-11-01 16:59       ` Rik van Riel
2000-11-01 21:03         ` Yann Dirson
2000-11-01 21:00           ` Andrea Arcangeli
2000-11-01 22:20             ` Yann Dirson
2000-11-06 21:56             ` Yann Dirson
2000-11-06 21:48               ` Jeff V. Merkey
2000-11-07 20:48                 ` Yann Dirson
2000-11-03 15:24           ` Ingo Oeser [this message]
2000-11-03 19:06             ` Marcelo Tosatti
2000-11-02  2:15       ` J . A . Magallon
2000-11-02 23:17         ` Andrea Arcangeli
2000-11-01 13:39 ` Miquel van Smoorenburg

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=20001103162409.S7204@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=ydirson@altern.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