linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Werner Almesberger <wa@almesberger.net>
Cc: Chris Ross <chris@tebibyte.org>,
	Andrea Arcangeli <andrea@novell.com>,
	Jesse Barnes <jbarnes@sgi.com>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	Andrew Morton <akpm@osdl.org>,
	Nick Piggin <piggin@cyberone.com.au>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH] Remove OOM killer from try_to_free_pages / all_unreclaimable braindamage
Date: Thu, 18 Nov 2004 15:44:38 +0100	[thread overview]
Message-ID: <1100789078.2635.73.camel@thomas> (raw)
In-Reply-To: <20041118070137.T28844@almesberger.net>

On Thu, 2004-11-18 at 07:01 -0300, Werner Almesberger wrote:
> > Too often at present the machine just doesn't know what to do,
> 
> See, that's exactly what I mean :-) So, why not just tell it ?
> "Hey, things are going to get a little rough for a while. Why
> don't you take a nap on that comfty swap disk while I clean up
> the house ?"
> 
> > [ * I just looked it up: "of, relating to, or resembling the mental or 
> > emotional state believed induced by the god Pan". Cool ]
> 
> Hmm, you're suggesting we follow Morpheus instead of Pan then ?
> And I always thought the OOM killer was more like Eris' work :-)

Hmm, what about embedded boxes without swap ? There you have only one
choice. Kill anything appropriate. 

I tested Marcellos, Andreas and Andrews changes and they all change the
trigger of the oom-killer to prevent the spurious unneccecary kills. But
in the case where an oom-kill is neccecary I still need my modifications
to the whom to kill decision and to the oom-killer itself.

1. Not to kill the innocent and maybe important processes like sshd

This one is solved by taking the childs into account.

2. To prevent overkill. 

This still happens with all the modifications I have tested. 
The szenario is that two processes request memory in an OOM situation.
The first caller to oom-kill is making room and then the second one is
also going to kill something. 

The oom-killer must be protected against reentrancy and it must check
for the free memory level before finally doing the kill.
See my previous patch in this thread.

BTW, I found out that hackbench is a quite good replacement for my real
application in triggering these corner cases. Just increase the number
of processes until you reach the limit of the machine.

tglx


--
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-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-11-18 14:44 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 20:01 Marcelo Tosatti
2004-11-05 23:32 ` Jesse Barnes
2004-11-05 23:47   ` Thomas Gleixner
2004-11-06  1:20   ` Andrea Arcangeli
2004-11-06  1:26     ` Nick Piggin
2004-11-06  1:36       ` Jesse Barnes
2004-11-06  1:50       ` Andrea Arcangeli
2004-11-06  9:47         ` Hugh Dickins
2004-11-06 10:53           ` Nick Piggin
2004-11-06 15:29             ` Andrea Arcangeli
2004-11-06 15:29           ` Andrea Arcangeli
2004-11-06 16:21             ` Hugh Dickins
2004-12-10  6:02               ` William Lee Irwin III
2004-11-06 11:37         ` Nikita Danilov
2004-11-06 15:32           ` Andrea Arcangeli
2004-11-06 16:54             ` Nikita Danilov
2004-11-06 17:44               ` Andrea Arcangeli
2004-11-06 19:24                 ` Nikita Danilov
2004-11-07  1:16                   ` Andrea Arcangeli
2004-11-06 10:11       ` Marcelo Tosatti
2004-11-06  1:55     ` Thomas Gleixner
2004-11-06 10:28       ` Marcelo Tosatti
2004-11-17 22:54       ` Werner Almesberger
2004-11-17 23:27         ` Chris Ross
2004-11-18  0:04           ` Werner Almesberger
2004-11-18  0:28             ` Chris Ross
2004-11-18  1:14               ` Werner Almesberger
2004-11-18  8:20                 ` Chris Ross
2004-11-18 10:01                   ` Werner Almesberger
2004-11-18 14:44                     ` Thomas Gleixner [this message]
2004-11-18 15:10                       ` Chris Friesen
2004-11-06 10:05     ` Marcelo Tosatti
2004-11-06 15:44       ` Andrea Arcangeli
2004-11-06 15:52         ` Arjan van de Ven
2004-11-06 17:09         ` Marcelo Tosatti
2004-11-07  0:48           ` Andrea Arcangeli
2004-11-07 11:21             ` Marcelo Tosatti
2004-11-06 12:53 ` [PATCH] Remove OOM killer Andries Brouwer
2004-11-06 10:41   ` Marcelo Tosatti
2004-11-07  9:26   ` Marko Macek
2004-11-08 16:27 ` [PATCH] Remove OOM killer from try_to_free_pages / all_unreclaimable braindamage Marcelo Tosatti

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=1100789078.2635.73.camel@thomas \
    --to=tglx@linutronix.de \
    --cc=akpm@osdl.org \
    --cc=andrea@novell.com \
    --cc=chris@tebibyte.org \
    --cc=jbarnes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=piggin@cyberone.com.au \
    --cc=wa@almesberger.net \
    /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