Thread (8 messages) 8 messages, 5 authors, 2012-10-16

Re: [PATCH] make GFP_NOTRACK flag unconditional

From: Glauber Costa <hidden>
Date: 2012-09-28 14:32:30
Also in: lkml

On 09/28/2012 06:28 PM, Christoph Lameter wrote:
On Fri, 28 Sep 2012, Glauber Costa wrote:
quoted
There was a general sentiment in a recent discussion (See
https://lkml.org/lkml/2012/9/18/258) that the __GFP flags should be
defined unconditionally. Currently, the only offender is GFP_NOTRACK,
which is conditional to KMEMCHECK.

This simple patch makes it unconditional.
__GFP_NOTRACK is only used in context where CONFIG_KMEMCHECK is defined?

If that is not the case then you need to define GFP_NOTRACK and substitute
it where necessary.
The flag is passed around extensively, but I was imagining the whole
point of that is that having the flag itself is harmless, and will be
ignored by the page allocator ?


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help