[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090504115335.9bc08587.akpm@linux-foundation.org>
Date: Mon, 4 May 2009 11:53:35 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Christoph Lameter <cl@...ux.com>
Cc: gorcunov@...il.com, mingo@...e.hu, mel@....ul.ie,
linux-kernel@...r.kernel.org, penberg@...helsinki.fi,
riel@...hat.com, rientjes@...gle.com, xemul@...nvz.org
Subject: Re: [PATCH -tip] mm: introduce __GFP_PANIC modifier
On Mon, 4 May 2009 09:47:45 -0400 (EDT)
Christoph Lameter <cl@...ux.com> wrote:
>
>
> Could you try to avoid consuming another GFP flag? __GFP_BITS_SHIFT is
> used elsewhere to figure out where to put miscellanous flags into the gfp
> mask. This is pretty limited right now and so the patch does work.
hm, yes, there are seven bits left.
afaict bit 3 (0x08) is unused?
Is __GFP_PANIC very useful? I expect it will permit a very small code
saving at a relatively small number of callsites, all of which are
__init anyway?
--
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