From: Rik van Riel <riel@conectiva.com.br>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-mm@kvack.org
Subject: Re: Discussion on my OOM killer API
Date: Thu, 19 Oct 2000 15:02:06 -0200 (BRDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0010191459320.19735-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <20001019122331.H840@nightmaster.csn.tu-chemnitz.de>
On Thu, 19 Oct 2000, Ingo Oeser wrote:
> You might remember the shortest "API" ever: The OOM killer API[1]
> I posted during the last round of hot discussion on OOM killing.
>
> What are the reasons of not including it? Its only a few lines
> for a complete API.
>
> I could have made it full blown with reference counting,
> automatic releasing old OOM killers and a nice proc interface[2]
> for letting the user say which he wants.
> 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 think we should be able to do this in less than half
a kb of kernel code and it might be able to get the last
few people who complain silenced as they try to produce
their own OOM killer ;)
[and we have a maintainer ... what else do we need ? ]
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/
next parent reply other threads:[~2000-10-19 17:02 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 [this message]
2000-10-26 20:47 ` Linus Torvalds
2000-10-26 21:16 ` Rik van Riel
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.0010191459320.19735-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