All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Peterson <dsp@llnl.gov>
To: Paul Jackson <pj@sgi.com>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	riel@surriel.com, nickpiggin@yahoo.com.au, ak@suse.de
Subject: Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations
Date: Fri, 28 Apr 2006 15:09:03 -0700	[thread overview]
Message-ID: <200604281509.03140.dsp@llnl.gov> (raw)
In-Reply-To: <20060427160250.a72cae11.pj@sgi.com>

On Thursday 27 April 2006 16:02, Paul Jackson wrote:
> I'm still a little surprised that this per-mm 'oom_notify' bit
> was needed to implement what I thought was a single, global
> system wide oom killer serializer.

I think the title "mm: serialize OOM kill operations" was probably a
poor choice of words.  It sounds like all I want to do is make sure
tasks enter the OOM killer one-at-a-time.  My goal is actually to
prevent further OOM kill operations until the OOM kill in progress
has caused the victim task to free its address space (i.e. clean out
its mm_struct).  That way we don't shoot more processes than necessary
to resolve the OOM condition.

WARNING: multiple messages have this Message-ID (diff)
From: Dave Peterson <dsp@llnl.gov>
To: Paul Jackson <pj@sgi.com>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	riel@surriel.com, nickpiggin@yahoo.com.au, ak@suse.de
Subject: Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations
Date: Fri, 28 Apr 2006 15:09:03 -0700	[thread overview]
Message-ID: <200604281509.03140.dsp@llnl.gov> (raw)
In-Reply-To: <20060427160250.a72cae11.pj@sgi.com>

On Thursday 27 April 2006 16:02, Paul Jackson wrote:
> I'm still a little surprised that this per-mm 'oom_notify' bit
> was needed to implement what I thought was a single, global
> system wide oom killer serializer.

I think the title "mm: serialize OOM kill operations" was probably a
poor choice of words.  It sounds like all I want to do is make sure
tasks enter the OOM killer one-at-a-time.  My goal is actually to
prevent further OOM kill operations until the OOM kill in progress
has caused the victim task to free its address space (i.e. clean out
its mm_struct).  That way we don't shoot more processes than necessary
to resolve the OOM condition.

--
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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-04-28 22:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 20:08 [PATCH 1/2 (repost)] mm: serialize OOM kill operations Dave Peterson
2006-04-27 20:08 ` Dave Peterson
2006-04-27 20:44 ` Paul Jackson
2006-04-27 20:44   ` Paul Jackson
2006-04-27 21:09   ` Andrew Morton
2006-04-27 21:09     ` Andrew Morton
2006-04-27 21:32     ` Dave Peterson
2006-04-27 21:32       ` Dave Peterson
2006-04-27 23:02     ` Paul Jackson
2006-04-27 23:02       ` Paul Jackson
2006-04-28 22:09       ` Dave Peterson [this message]
2006-04-28 22:09         ` Dave Peterson
2006-04-27 22:56 ` Andrew Morton
2006-04-27 22:56   ` Andrew Morton
2006-04-28 21:59   ` Dave Peterson
2006-04-28 21:59     ` Dave Peterson
2006-04-28 22:16     ` Andrew Morton
2006-04-28 22:16       ` Andrew Morton
2006-04-28 22:24       ` Dave Peterson
2006-04-28 22:24         ` Dave Peterson

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=200604281509.03140.dsp@llnl.gov \
    --to=dsp@llnl.gov \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pj@sgi.com \
    --cc=riel@surriel.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 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.