public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Paul Jackson <pj@sgi.com>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Terminate process that fails on a constrained allocation
Date: Wed, 8 Feb 2006 20:05:12 +0100	[thread overview]
Message-ID: <200602082005.12657.ak@suse.de> (raw)
In-Reply-To: <20060208105714.15bb4bb2.pj@sgi.com>

On Wednesday 08 February 2006 19:57, Paul Jackson wrote:
> > No it only disables the oom killer for constrained allocations.
> 
> But on many big numa systems, the way they are administered,
> that affectively disables the oom killer.

I guess it won't matter because they are administrated with appropiate ulimits
I guess. And to be honest the OOM killer never really worked all that
well, so it's not a big loss.

[still often wish we had that "global virtual memory ulimit for uid"]


> I've yet to be convinced that the oom killer is our friend,
> and half of me (not seriously) is almost wishing it were
> gone.

It's more than half of me near seriously agreeing with you.

> Would another option be to continue to fine tune the heuristics
> that the oom killer uses to pick its next victim?
> 
> What situation did you hit that motivated this change?

It's a long known design bug of the NUMA policy, but it recently 
hit with some test program again.


-Andi

  parent reply	other threads:[~2006-02-08 19:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 18:05 Terminate process that fails on a constrained allocation Christoph Lameter
2006-02-08 18:13 ` Andi Kleen
2006-02-08 18:34   ` Paul Jackson
2006-02-08 18:54     ` Christoph Lameter
2006-02-08 19:01       ` Andi Kleen
2006-02-08 19:15         ` Christoph Lameter
2006-02-08 18:33 ` Paul Jackson
2006-02-08 18:42   ` Christoph Lameter
2006-02-08 18:57     ` Paul Jackson
2006-02-08 19:02       ` Christoph Lameter
2006-02-08 19:05       ` Andi Kleen [this message]
2006-02-08 20:22         ` Paul Jackson
2006-02-08 20:36           ` Christoph Lameter
2006-02-08 20:55             ` Paul Jackson
2006-02-08 21:01               ` Andi Kleen
2006-02-08 21:03                 ` Paul Jackson
2006-02-08 21:21                   ` Andi Kleen
2006-02-08 21:39                     ` Andrew Morton
2006-02-08 22:11                       ` Christoph Lameter
2006-02-08 22:41                         ` Andi Kleen
2006-02-08 23:29                           ` Christoph Lameter
2006-02-08 23:35                           ` Andrew Morton
2006-02-08 22:48                         ` Christoph Lameter
2006-02-08 23:28                       ` Christoph Lameter
2006-02-08 23:43                         ` Andrew Morton
2006-02-08 23:54                           ` Christoph Lameter
2006-02-08 23:57                             ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-02-08 20:14 linux

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=200602082005.12657.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=clameter@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.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