[<prev] [next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1507141426410.16182@chino.kir.corp.google.com>
Date: Tue, 14 Jul 2015 14:28:21 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: Mikulas Patocka <mpatocka@...hat.com>,
Mike Snitzer <msnitzer@...hat.com>,
"Alasdair G. Kergon" <agk@...hat.com>,
Edward Thornber <thornber@...hat.com>,
Vivek Goyal <vgoyal@...hat.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, dm-devel@...hat.com,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: [patch] mm: improve __GFP_NORETRY comment based on implementation
Explicitly state that __GFP_NORETRY will attempt direct reclaim and memory
compaction before returning NULL and that the oom killer is not called in
the current implementation of the page allocator.
Signed-off-by: David Rientjes <rientjes@...gle.com>
---
include/linux/gfp.h | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/linux/gfp.h b/include/linux/gfp.h
--- a/include/linux/gfp.h
+++ b/include/linux/gfp.h
@@ -63,7 +63,10 @@ struct vm_area_struct;
* but it is definitely preferable to use the flag rather than opencode endless
* loop around allocator.
*
- * __GFP_NORETRY: The VM implementation must not retry indefinitely.
+ * __GFP_NORETRY: The VM implementation must not retry indefinitely and will
+ * return NULL when direct reclaim and memory compaction has failed to allow the
+ * allocation to succeed. The OOM killer is not called with the current
+ * implementation.
*
* __GFP_MOVABLE: Flag that this page will be movable by the page migration
* mechanism or reclaimed
--
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