[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200905041702.23291.rjw@sisk.pl>
Date: Mon, 4 May 2009 17:02:22 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: David Rientjes <rientjes@...gle.com>
Cc: Wu Fengguang <fengguang.wu@...el.com>,
linux-pm@...ts.linux-foundation.org,
Andrew Morton <akpm@...ux-foundation.org>, pavel@....cz,
torvalds@...ux-foundation.org, jens.axboe@...cle.com,
alan-jenkins@...fmail.co.uk, linux-kernel@...r.kernel.org,
kernel-testers@...r.kernel.org
Subject: Re: [PATCH 1/5] mm: Add __GFP_NO_OOM_KILL flag
On Monday 04 May 2009, David Rientjes wrote:
> On Mon, 4 May 2009, Rafael J. Wysocki wrote:
>
> > Index: linux-2.6/mm/page_alloc.c
> > ===================================================================
> > --- linux-2.6.orig/mm/page_alloc.c
> > +++ linux-2.6/mm/page_alloc.c
> > @@ -1620,7 +1620,8 @@ nofail_alloc:
> > }
> >
> > /* The OOM killer will not help higher order allocs so fail */
> > - if (order > PAGE_ALLOC_COSTLY_ORDER) {
> > + if (order > PAGE_ALLOC_COSTLY_ORDER ||
> > + (gfp_mask & __GFP_NO_OOM_KILL)) {
> > clear_zonelist_oom(zonelist, gfp_mask);
> > goto nopage;
> > }
>
> This is inconsistent because __GFP_NO_OOM_KILL now implies __GFP_NORETRY
> (the "goto nopage" above), but only for allocations with __GFP_FS set and
> __GFP_NORETRY clear.
Well, what would you suggest?
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists