mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Morton <chromi@cyberspace.org>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
	Martin Dalecki <dalecki@evision-ventures.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>, linux-kernel@vger.kernel.org
Subject: Re: OOM killer???
Date: Tue, 27 Mar 2001 19:37:32 +0100	[thread overview]
Message-ID: <l0313033bb6e68d4f8fbb@[192.168.239.101]> (raw)
In-Reply-To: <20010327200830.C8133@nightmaster.csn.tu-chemnitz.de>
In-Reply-To: <3AC09480.E8317507@evision-ventures.com>; from dalecki@evision-ventures.com on Tue, Mar 27, 2001 at 03:24:16PM +0200 <l03130332b6e632432b9f@[192.168.239.101]> <3AC09480.E8317507@evision-ventures.com>

>If we use my OOM killer API, this patch would be a module and
>could have module parameters to select that.
>
>Johnathan: I URGE you to apply my patch before adding OOM killer
>   stuff. What's wrong with it, that you cannot use it? ;-)
>
>It is easy to add configurables to a module and play with them
>WITHOUT recompiling.

Thanks for reminding me - I'll look into it on the plane and see what I can
do with it.

>e.g. My important matlab calculation, which runs in user mode
>should not be killed. But killing a local webserver, which serves
>my help system is ok (because I will not loose work, and might
>get it over the net, if there is a problem).
>
>So as Rik stated: The OOM killer cannot suit all people, so it
>has to be configurable, to be OOM kill, not overkill ;-)

Yes, configurability is probably a very good idea.  However, it would be
best to include a good set of general parameters in the kernel itself, so
the set of average systems needs as little tweaking as possible.  One
cannot expect every sysadmin to be familiar with these arcane (and rarely
actually used) parameters, so being able to select "server", "batch",
"workstation", "embedded" and so on would help massively.

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@cyberspace.org  (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----



  parent reply	other threads:[~2001-03-27 18:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 10:59 Rogier Wolff
2001-03-27 12:14 ` Jonathan Morton
2001-03-27 13:24   ` Martin Dalecki
2001-03-27 18:08     ` Ingo Oeser
2001-03-27 19:07       ` Martin Dalecki
2001-03-27 19:55         ` Andreas Dilger
2001-03-27 21:13           ` Andreas Rogge
2001-03-27 13:57   ` Jonathan Morton
2001-03-27 15:31   ` Jonathan Lundell
2001-03-27 16:07     ` Config bug? In 2.2.19 CONFIG_RTL8139 depends on CONFIG_EXPERIMENTAL Greg Ingram
2001-03-27 16:14       ` Jeff Garzik
2001-03-27 16:37         ` [PATCH] 2.2.19 drivers/net/Config.in Greg Ingram
2001-03-27 18:37   ` Jonathan Morton [this message]
     [not found] <200103282138.f2SLcT824292@webber.adilger.int>
2001-03-29  9:29 ` OOM killer??? Dr. Michael Weller
2001-03-29 11:01   ` Guest section DW
2001-03-29 12:02     ` Sean Hunter
2001-03-29 12:57       ` Guest section DW
2001-03-29 15:41     ` David Konerding
2001-03-29 17:52       ` David Lang
2001-03-29 17:21     ` Stephen Satchell
2001-03-30  2:26     ` Michael Peddemors
2001-03-30 14:48       ` J. Scott Kasten
2001-03-29 13:53   ` Szabolcs Szakacsits
2001-03-29 15:01     ` Dr. Michael Weller
2001-03-29 16:29       ` Szabolcs Szakacsits
2001-03-29 16:51       ` Szabolcs Szakacsits
2001-03-29 16:22 Jesse Pollard
2001-03-29 19:20 Jesse Pollard

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='l0313033bb6e68d4f8fbb@[192.168.239.101]' \
    --to=chromi@cyberspace.org \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=dalecki@evision-ventures.com \
    --cc=ingo.oeser@informatik.tu-chemnitz.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

all inboxes | Powered by JetHome®