diff options
| author | David Rientjes <[email protected]> | 2015-09-08 15:00:31 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2015-09-08 15:35:28 -0700 |
| commit | 28c015d07507e164d93b33498b4e482ff81c0e9b (patch) | |
| tree | b413cac1d2dcff31395acf5c47403c1e27019237 /include/linux | |
| parent | 998ef75ddb5709bbea0bf1506cd2717348a3c647 (diff) | |
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.
[[email protected]: s/has/have/]
Signed-off-by: David Rientjes <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'include/linux')
| -rw-r--r-- | include/linux/gfp.h | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/include/linux/gfp.h b/include/linux/gfp.h index ad35f300b9a4..3bd64b115999 100644 --- 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 have 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 |