From: Rik van Riel <riel@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Nick Piggin <npiggin@suse.de>,
Christoph Lameter <cl@linux-foundation.org>,
Dave Hansen <dave@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch -mmotm] mm: invoke oom killer for __GFP_NOFAIL
Date: Sun, 10 May 2009 19:42:35 -0400 [thread overview]
Message-ID: <4A07666B.5020706@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0905091544470.6884@chino.kir.corp.google.com>
David Rientjes wrote:
> The oom killer must be invoked regardless of the order if the allocation
> is __GFP_NOFAIL, otherwise it will loop forever when reclaim fails to
> free some memory.
>
> Cc: Mel Gorman <mel@csn.ul.ie>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Nick Piggin <npiggin@suse.de>
> Cc: Christoph Lameter <cl@linux-foundation.org>
> Cc: Dave Hansen <dave@linux.vnet.ibm.com>
> Signed-off-by: David Rientjes <rientjes@google.com>
Acked-by: Rik van Riel <riel@redhat.com>
--
All rights reversed.
next prev parent reply other threads:[~2009-05-10 23:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 22:46 [patch -mmotm] mm: invoke oom killer for __GFP_NOFAIL David Rientjes
2009-05-10 23:42 ` Rik van Riel [this message]
2009-05-11 7:29 ` Minchan Kim
2009-05-11 8:40 ` David Rientjes
2009-05-11 9:12 ` Minchan Kim
2009-05-11 11:21 ` Minchan Kim
2009-05-11 13:38 ` Mel Gorman
2009-05-11 14:00 ` Minchan Kim
2009-05-11 19:32 ` David Rientjes
2009-05-11 23:48 ` Minchan Kim
2009-05-11 21:32 ` Mel Gorman
2009-05-11 23:41 ` Minchan Kim
2009-05-11 10:40 ` Mel Gorman
2009-05-11 19:37 ` David Rientjes
2009-05-11 20:40 ` Andrew Morton
2009-05-12 12:42 ` Jens Axboe
2009-05-12 13:05 ` Nick Piggin
2009-05-12 16:37 ` Jens Axboe
2009-05-12 16:49 ` Nick Piggin
2009-05-12 17:35 ` Jens Axboe
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=4A07666B.5020706@redhat.com \
--to=riel@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.de \
--cc=rientjes@google.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