linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>, linux-mm@kvack.org
Subject: Re: Discussion on my OOM killer API
Date: Thu, 26 Oct 2000 19:16:38 -0200 (BRDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0010261857580.15696-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.10.10010261345320.2575-100000@penguin.transmeta.com>

On Thu, 26 Oct 2000, Linus Torvalds wrote:
> On Thu, 19 Oct 2000, Rik van Riel wrote:
> > > I'm also willing to maintain it ;-)
> > 
> > Linus, how would you feel about an interface that allows
> > people to insomd/rmmod their own OOM handler ?
> 
> I hate the idea.

*grin*

I agree with that, except for one small point...

> I dislike that kind of approach in general. I don't like plug-in
> schedulers, etc either. I think it's a cop-out, saying that we
> cannot do a good enough job, and claiming that it's such a
> difficult problem that we should let the user decide.

... the generic OOM killer we have in the system right now
should do a good job in most of the cases, but I've heard
from a number of people who would like to have the OOM killer
do something "special" for their system.

For instance, they want to have student programs killed before
staff programs, or want to be able to specify some priveledged
processes that will never be killed (or do other things that
we probably don't want to have in the generic killer).

> In short, it's one of those things that sounds like a good idea,
> but that results in absolute crap in the end.

Sure, but the idea is to keep this absolute crap out of
the kernel and local to the systems where people need
to replace the OOM killer because of special reasons ;)

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
       -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/		http://www.surriel.com/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-10-26 21:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20001019122331.H840@nightmaster.csn.tu-chemnitz.de>
2000-10-19 17:02 ` Rik van Riel
2000-10-26 20:47   ` Linus Torvalds
2000-10-26 21:16     ` Rik van Riel [this message]
2000-10-26 22:33       ` Mark Hahn
2000-10-26 23:58       ` James Sutherland
2000-10-27  0:10         ` Linus Torvalds
2000-10-27  6:46           ` James Sutherland
2000-10-27  7:39             ` Gábor Lénárt
2000-10-27 13:54               ` James Sutherland
2000-10-27 17:10         ` Ingo Oeser
2000-10-27 17:36           ` James Sutherland
2000-10-27 22:12             ` jfm2
2000-10-27 22:11               ` James Sutherland
2000-10-27 22:43                 ` jfm2
2000-10-27 22:51                   ` James Sutherland
2000-10-28  4:48                 ` Jeremy Fitzhardinge
2000-10-28  7:29                   ` James Sutherland
2000-10-30  9:02               ` G?bor L?n?rt
2000-10-30  9:41                 ` James Sutherland
2000-10-30  9:53                   ` G?bor L?n?rt
2000-10-30 12:18                     ` J.A. Sutherland
2000-10-29 19:30             ` Ingo Oeser
2000-10-29 20:41               ` James Sutherland

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=Pine.LNX.4.21.0010261857580.15696-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@transmeta.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