public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: rusty@linux.co.intel.com
Cc: riel@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Enabling other oom schemes
Date: Fri, 12 Sep 2003 00:50:30 -0400	[thread overview]
Message-ID: <1063342229.700.240.camel@localhost> (raw)
In-Reply-To: <200309120219.h8C2JANc004514@penguin.co.intel.com>

On Thu, 2003-09-11 at 22:19, Rusty Lynch wrote:

> The patch works (although by looking over oom_kill.c, I'm sure oom_panic.c
> will panic too soon), but it is really only a quick hack to see how people
> feel about such an approach.

I like this a _lot_, it is something I have thought about doing, and
something we have a need for at MontaVista.

But I think its a lot more useful if we have alternative overcommit
modes to use with it.

An oom_nop might be a good idea.  But some different policies, i.e. ones
with more determinism but less smarts, are interesting.

	Robert Love



  parent reply	other threads:[~2003-09-12  4:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12  2:19 [RFC] Enabling other oom schemes Rusty Lynch
2003-09-12  4:18 ` Rahul Karnik
2003-09-12  4:31   ` Chris Friesen
2003-09-12  4:40     ` Rahul Karnik
2003-09-12  4:48       ` Robert Love
2003-09-12 11:18     ` Helge Hafting
2003-09-12 14:07       ` Chris Friesen
2003-09-12  4:47   ` Robert Love
2003-09-12  4:50 ` Robert Love [this message]
2003-09-12 10:42   ` Alan Cox
2003-09-12  8:58 ` Tvrtko A. Uršulin
2003-09-13  2:21   ` Rusty Lynch
2003-09-15 10:59     ` Tvrtko A. Uršulin
2003-09-13 17:48 ` Jamie Lokier
2003-09-13 20:52   ` Robert Love
2003-09-13 22:04     ` Helge Hafting
2003-09-14  0:55       ` Robert Love
2003-09-14  9:12         ` Helge Hafting
2003-09-14  5:28     ` Chris Friesen
2003-09-15  0:11     ` Mike S

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=1063342229.700.240.camel@localhost \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=rusty@linux.co.intel.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