linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: James Sutherland <jas88@cam.ac.uk>
Cc: Rik van Riel <riel@conectiva.com.br>,
	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 17:10:14 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10010261708490.3053-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10010270056590.11273-100000@dax.joh.cam.ac.uk>


On Fri, 27 Oct 2000, James Sutherland wrote:
> 
> Which begs the question, where did the userspace OOM policy daemon go? It,
> coupled with Rik's simple in-kernel last-ditch handler, should cover most
> eventualities without the need for nasty kernel kludges.

I agree. Possibly with help to the user-space OOM thing. We should
probably implement the same SIGDANGER that some other Unixes have, and
then anybody can implement their own low-on-memory thing by having a
user-mode server that does a mlockall() and reacts to SIGDANGER by
spraying anything it wants with kill(9)'s.

		Linus

--
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-27  0:10 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
2000-10-26 22:33       ` Mark Hahn
2000-10-26 23:58       ` James Sutherland
2000-10-27  0:10         ` Linus Torvalds [this message]
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.10.10010261708490.3053-100000@penguin.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=jas88@cam.ac.uk \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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