linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Schmidt <will_schmidt@vnet.ibm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH for review] [11/48] x86_64: During VM oom condition, kill all threads in process group
Date: Thu, 19 Jul 2007 10:03:09 -0500	[thread overview]
Message-ID: <1184857389.22237.20.camel@farscape.rchland.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707191614180.7377@anakin>

On Thu, 2007-07-19 at 16:14 +0200, Geert Uytterhoeven wrote:
> On Thu, 19 Jul 2007, Christoph Hellwig wrote:
> > On Thu, Jul 19, 2007 at 03:48:40PM +0200, Andi Kleen wrote:
> > > From: Will Schmidt <will_schmidt@vnet.ibm.com>
> > > 
> > > During a VM oom condition, kill all threads in the process group.
> > > 
> > > We have had complaints where a threaded application is left in a bad state
> > > after one of it's threads is killed when we hit a VM: out_of_memory condition.
> > > 
> > > Killing just one of the process threads can leave the application in a bad
> > > state, whereas killing the entire process group would allow for the
> > > application to restart, or otherwise handled, and makes it very obvious that
> > > something has gone wrong.
> > > 
> > > This change allows the entire process group to be taken down, rather than just
> > > the one thread.
> > 
> > Shouldn't we have one patc hthat does this for every architecture instead
> > of going through arch maintainers and probably losing half of them?
> 
> Yes, please ;-)

Ok, i'm convinced. :-)      I'll spin up an all-arch encompassing patch
in the next day or so. 

-Will



> 
> Gr{oetje,eeting}s,
> 
> 						Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> return -EMAINTAINER_TOO_BUSY


  reply	other threads:[~2007-07-19 15:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070719348.540885000@suse.de>
     [not found] ` <20070719134840.47B5114E6E@wotan.suse.de>
2007-07-19 14:04   ` [PATCH for review] [11/48] x86_64: During VM oom condition, kill all threads in process group Christoph Hellwig
2007-07-19 14:14     ` Geert Uytterhoeven
2007-07-19 15:03       ` Will Schmidt [this message]
2007-07-23 18:09       ` [PATCH respin, was PATCH for review] " Will Schmidt
2007-07-23 21:16         ` Andrew Morton
2007-07-24 14:28           ` Will Schmidt
2007-07-24 14:31             ` Christoph Hellwig
2007-07-31  9:31         ` Pavel Machek
2007-07-31 14:55           ` Will Schmidt

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=1184857389.22237.20.camel@farscape.rchland.ibm.com \
    --to=will_schmidt@vnet.ibm.com \
    --cc=ak@suse.de \
    --cc=geert@linux-m68k.org \
    --cc=hch@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).