linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Will Schmidt <will_schmidt@vnet.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Anton Blanchard <anton@samba.org>
Subject: Re: During VM oom condition, kill all threads in process group
Date: Wed, 17 Oct 2007 11:13:08 -0500	[thread overview]
Message-ID: <1192637589.18159.372.camel@farscape.rchland.ibm.com> (raw)
In-Reply-To: <20071016224147.GB29378@wotan.suse.de>

On Wed, 2007-10-17 at 00:41 +0200, Nick Piggin wrote:
> Hi,
> 
Hi Nick, 

> What architecture, filesystems, and workload did you observe problems with?
> Did you discover which allocation was failing?

Powerpc architecture, running GPFS.   Sadly, I dont have any real
details on the workload that actually generated the oom condition, so
dont know what allocation was failing, etc.

> I have a patch for this, but wasn't really pushing it hard because it's
> pretty unlikely for x86 and standard filesystems to oom from here...

Yeah, I suspect pretty unlikely for any architecture to get there.
Powerpc in addition to x86 anyway..  :-)   For my test purposes I added
debug code to force taking that code path.

Thanks,
-Will

> Thanks,
> Nick
> 

--
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:[~2007-10-17 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 22:41 Nick Piggin
2007-10-17 16:13 ` Will Schmidt [this message]

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=1192637589.18159.372.camel@farscape.rchland.ibm.com \
    --to=will_schmidt@vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@samba.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=torvalds@linux-foundation.org \
    /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