All of
 help / color / mirror / Atom feed
From: Andrew Morton <>
To: David Rientjes <>
Cc: Tetsuo Handa <>,
	Michal Hocko <>,
	Johannes Weiner <>,,,,,,,
	Sergey Senozhatsky <>,
	Petr Mladek <>,
	Sergey Senozhatsky <>,
	Steven Rostedt <>
Subject: Re: [PATCH] mm,oom: Use timeout based back off.
Date: Wed, 24 Oct 2018 15:54:54 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, 22 Oct 2018 14:11:10 -0700 (PDT) David Rientjes <> wrote:

> > Michal has been refusing timeout based approach, but I don't think this
> > is something we have to be frayed around the edge about possibility of
> > overlooking races/bugs just because Michal does not want to use timeout.
> > I believe that timeout based back off is the only approach we can use
> > for now.
> > 
> I've proposed patches that have been running for months in a production 
> environment that make the oom killer useful without serially killing many 
> processes unnecessarily.  At this point, it is *much* easier to just fork 
> the oom killer logic rather than continue to invest time into fixing it in 
> Linux.  That's unfortunate because I'm sure you realize how problematic 
> the current implementation is, how abusive it is, and have seen its 
> effects yourself.  I admire your persistance in trying to fix the issues 
> surrounding the oom killer, but have come to the conclusion that forking 
> it is a much better use of time.

The oom killer is, I think, fairly standalone and it shouldn't be too
hard to add the infrastructure to make the whole thing pluggable.  At
runtime, not at build time.

But it is a last resort - it will result in fragmented effort and
difficult decisions for everyone regarding which should be used.

There has been a lot of heat and noise and confusion and handwaving in
all of this.  What we're crying out for is simple testcases which
everyone can run.  Find a problem, write the testcase, distribute that.
Develop a solution for that testcase then move on to the next one.

  parent reply	other threads:[~2018-10-24 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 10:57 Tetsuo Handa
2018-10-22 21:11 ` David Rientjes
2018-10-23  5:56   ` Michal Hocko
2018-10-24 22:54   ` Andrew Morton [this message]
2018-10-25  7:11     ` Michal Hocko

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] mm,oom: Use timeout based back off.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.