[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090509083116.GC3656@elte.hu>
Date: Sat, 9 May 2009 10:31:16 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Pekka Enberg <penberg@...helsinki.fi>
Cc: Christoph Lameter <cl@...ux-foundation.org>,
akpm@...ux-foundation.org, gorcunov@...nvz.org,
kosaki.motohiro@...fujitsu.com, mel@....ul.ie, riel@...hat.com,
linux-kernel@...r.kernel.org, rientjes@...gle.com
Subject: Re: [PATCH 1/2] mm: Introduce GFP_PANIC for early-boot allocations
* Pekka Enberg <penberg@...helsinki.fi> wrote:
> On Fri, 2009-05-08 at 11:29 -0400, Christoph Lameter wrote:
> > On Fri, 8 May 2009, Pekka Enberg wrote:
> >
> > > From: Pekka Enberg <penberg@...helsinki.fi>
> > >
> > > This patch introduces a GFP_PANIC flag that can be used as an annotation
> > > that an early-boot call to kmalloc() or alloc_pages() is expected to
> > > never fail.
> >
> > I think the early-boot requirement needs to be dropped. Make this safe to
> > be used at anytime.
>
> OK, here's an updated patch description:
>
> Subject: [PATCH 1/2] mm: Introduce GFP_PANIC
> From: Pekka Enberg <penberg@...helsinki.fi>
>
> This patch introduces a GFP_PANIC flag that can be used as an annotation
> that a kmalloc() or alloc_pages() call is expected to never fail which is
> useful for early-boot code, for example.
>
> To save one GFP flag bit, use a combination of __GFP_NOFAIL and
> __GFP_NOREPEAT to make sure we always end up in the "nopage" path of the
> page allocator if an allocation fails.
>
> [ gorcunov@...nvz.org: initial version of the patch ]
> Cc: Christoph Lameter <cl@...ux-foundation.org>
> Cc: David Rientjes <rientjes@...gle.com>
> Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
> Cc: Mel Gorman <mel@....ul.ie>
> Cc: Rik van Riel <riel@...hat.com>
> Signed-off-by: Pekka Enberg <penberg@...helsinki.fi>
Thanks Pekka for taking care of this,
Acked-by: Ingo Molnar <mingo@...e.hu>
Ingo
--
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