public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dan Mann" <daniel_b_mann@hotmail.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: VM nuisance
Date: Sun, 12 Aug 2001 19:05:11 -0400	[thread overview]
Message-ID: <OE18Y30kkZIhTrBoe2U00004e33@hotmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108121506100.18332-100000@druid.if.uj.edu.pl>

Rik Said:

> > No.  The problem is that whenever I change something to
> > the OOM killer I get flamed.
> >
> > Both by the people for whom the OOM killer kicks in too
> > early and by the people for whom the OOM killer now doesn't
> > kick in.
> >
> > I haven't got the faintest idea how to come up with an OOM
> > killer which does the right thing for everybody.

Would there be a way that you could have a proc interface to adjust the
sensitivity of the OOM killer so that users could raise or lower the
threshold that causes OOM killer activation?  Hopefully you wouldn't get any
flak for that unless users start blaming you for their own settings :-)

Most people would just use the standard setting that you provide...but
others that felt the need could change it on their system.

Dan

  parent reply	other threads:[~2001-08-12 23:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-11  1:30 VM nuisance David Ford
2001-08-11  2:48 ` Rik van Riel
2001-08-11  2:59   ` H. Peter Anvin
2001-08-11  4:17     ` Rik van Riel
2001-08-11  4:40       ` David Ford
2001-08-11  4:46         ` Rik van Riel
2001-08-11  4:41       ` safemode
2001-08-11  5:00       ` H. Peter Anvin
2001-08-11 13:13     ` Alan Cox
2001-08-11 15:39       ` David Ford
2001-08-11  3:50   ` safemode
2001-08-12 13:09   ` Maciej Zenczykowski
2001-08-12 13:45     ` Rik van Riel
2001-08-16 23:29       ` Justin A
2001-08-17  0:06         ` Dr. Kelsey Hudson
2001-08-17  0:24           ` Justin A
2001-08-17  2:54             ` Dr. Kelsey Hudson
2001-08-12 23:05     ` Dan Mann [this message]
     [not found]   ` <9l5v9a$ha9$1@ns1.clouddancer.com>
2001-08-13  0:01     ` Colonel
2001-08-13 14:32   ` dean gaudet
2001-08-13 19:47     ` Brian
2001-08-14  8:27     ` Helge Hafting
2001-08-17 13:34       ` Szabolcs Szakacsits
2001-08-17 17:29         ` Rik van Riel
2001-08-14 14:00 ` "VM watchdog"? [was Re: VM nuisance] Pavel Machek
2001-08-16 22:24   ` Jakob Østergaard
2001-08-17  1:26     ` David Ford
2001-08-17  1:41       ` Jakob Østergaard
     [not found]       ` <9li6sf$h5$1@ns1.clouddancer.com>
2001-08-17  9:04         ` Colonel
2001-08-17 20:38           ` David Ford
     [not found] <20010811035112.59EC438D01@perninha.conectiva.com.br>
2001-08-11  3:52 ` VM nuisance Rik van Riel
     [not found] <no.id>
2001-08-11 16:45 ` Alan Cox

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=OE18Y30kkZIhTrBoe2U00004e33@hotmail.com \
    --to=daniel_b_mann@hotmail.com \
    --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