2005-04-16 22:20:36 +00:00
|
|
|
#ifndef __LINUX_GFP_H
|
|
|
|
#define __LINUX_GFP_H
|
|
|
|
|
2014-01-23 23:52:54 +00:00
|
|
|
#include <linux/mmdebug.h>
|
2005-04-16 22:20:36 +00:00
|
|
|
#include <linux/mmzone.h>
|
|
|
|
#include <linux/stddef.h>
|
|
|
|
#include <linux/linkage.h>
|
2009-03-13 13:13:37 +00:00
|
|
|
#include <linux/topology.h>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
struct vm_area_struct;
|
|
|
|
|
2016-03-15 21:55:45 +00:00
|
|
|
/*
|
|
|
|
* In case of changes, please don't forget to update
|
2016-03-15 21:55:49 +00:00
|
|
|
* include/trace/events/gfpflags.h and tools/perf/builtin-kmem.c
|
2016-03-15 21:55:45 +00:00
|
|
|
*/
|
|
|
|
|
2010-10-26 21:22:04 +00:00
|
|
|
/* Plain integer GFP bitmasks. Do not use this directly. */
|
|
|
|
#define ___GFP_DMA 0x01u
|
|
|
|
#define ___GFP_HIGHMEM 0x02u
|
|
|
|
#define ___GFP_DMA32 0x04u
|
|
|
|
#define ___GFP_MOVABLE 0x08u
|
2015-11-07 00:28:18 +00:00
|
|
|
#define ___GFP_RECLAIMABLE 0x10u
|
2010-10-26 21:22:04 +00:00
|
|
|
#define ___GFP_HIGH 0x20u
|
|
|
|
#define ___GFP_IO 0x40u
|
|
|
|
#define ___GFP_FS 0x80u
|
|
|
|
#define ___GFP_COLD 0x100u
|
|
|
|
#define ___GFP_NOWARN 0x200u
|
|
|
|
#define ___GFP_REPEAT 0x400u
|
|
|
|
#define ___GFP_NOFAIL 0x800u
|
|
|
|
#define ___GFP_NORETRY 0x1000u
|
2012-07-31 23:44:03 +00:00
|
|
|
#define ___GFP_MEMALLOC 0x2000u
|
2010-10-26 21:22:04 +00:00
|
|
|
#define ___GFP_COMP 0x4000u
|
|
|
|
#define ___GFP_ZERO 0x8000u
|
|
|
|
#define ___GFP_NOMEMALLOC 0x10000u
|
|
|
|
#define ___GFP_HARDWALL 0x20000u
|
|
|
|
#define ___GFP_THISNODE 0x40000u
|
2015-11-07 00:28:21 +00:00
|
|
|
#define ___GFP_ATOMIC 0x80000u
|
2016-01-14 23:18:12 +00:00
|
|
|
#define ___GFP_ACCOUNT 0x100000u
|
Revert "revert "Revert "mm: remove __GFP_NO_KSWAPD""" and associated damage
This reverts commits a50915394f1fc02c2861d3b7ce7014788aa5066e and
d7c3b937bdf45f0b844400b7bf6fd3ed50bac604.
This is a revert of a revert of a revert. In addition, it reverts the
even older i915 change to stop using the __GFP_NO_KSWAPD flag due to the
original commits in linux-next.
It turns out that the original patch really was bogus, and that the
original revert was the correct thing to do after all. We thought we
had fixed the problem, and then reverted the revert, but the problem
really is fundamental: waking up kswapd simply isn't the right thing to
do, and direct reclaim sometimes simply _is_ the right thing to do.
When certain allocations fail, we simply should try some direct reclaim,
and if that fails, fail the allocation. That's the right thing to do
for THP allocations, which can easily fail, and the GPU allocations want
to do that too.
So starting kswapd is sometimes simply wrong, and removing the flag that
said "don't start kswapd" was a mistake. Let's hope we never revisit
this mistake again - and certainly not this many times ;)
Acked-by: Mel Gorman <mgorman@suse.de>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Cc: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-12-10 18:51:16 +00:00
|
|
|
#define ___GFP_NOTRACK 0x200000u
|
2015-11-07 00:28:21 +00:00
|
|
|
#define ___GFP_DIRECT_RECLAIM 0x400000u
|
Revert "revert "Revert "mm: remove __GFP_NO_KSWAPD""" and associated damage
This reverts commits a50915394f1fc02c2861d3b7ce7014788aa5066e and
d7c3b937bdf45f0b844400b7bf6fd3ed50bac604.
This is a revert of a revert of a revert. In addition, it reverts the
even older i915 change to stop using the __GFP_NO_KSWAPD flag due to the
original commits in linux-next.
It turns out that the original patch really was bogus, and that the
original revert was the correct thing to do after all. We thought we
had fixed the problem, and then reverted the revert, but the problem
really is fundamental: waking up kswapd simply isn't the right thing to
do, and direct reclaim sometimes simply _is_ the right thing to do.
When certain allocations fail, we simply should try some direct reclaim,
and if that fails, fail the allocation. That's the right thing to do
for THP allocations, which can easily fail, and the GPU allocations want
to do that too.
So starting kswapd is sometimes simply wrong, and removing the flag that
said "don't start kswapd" was a mistake. Let's hope we never revisit
this mistake again - and certainly not this many times ;)
Acked-by: Mel Gorman <mgorman@suse.de>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Cc: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-12-10 18:51:16 +00:00
|
|
|
#define ___GFP_OTHER_NODE 0x800000u
|
|
|
|
#define ___GFP_WRITE 0x1000000u
|
2015-11-07 00:28:21 +00:00
|
|
|
#define ___GFP_KSWAPD_RECLAIM 0x2000000u
|
2012-12-12 21:51:56 +00:00
|
|
|
/* If the above are modified, __GFP_BITS_SHIFT may need updating */
|
2010-10-26 21:22:04 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
2015-11-07 00:28:43 +00:00
|
|
|
* Physical address zone modifiers (see linux/mmzone.h - low four bits)
|
2006-09-26 06:31:14 +00:00
|
|
|
*
|
|
|
|
* Do not put any conditional on these. If necessary modify the definitions
|
2010-05-24 21:32:44 +00:00
|
|
|
* without the underscores and use them consistently. The definitions here may
|
2006-09-26 06:31:14 +00:00
|
|
|
* be used in bit comparisons.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
2010-10-26 21:22:04 +00:00
|
|
|
#define __GFP_DMA ((__force gfp_t)___GFP_DMA)
|
|
|
|
#define __GFP_HIGHMEM ((__force gfp_t)___GFP_HIGHMEM)
|
|
|
|
#define __GFP_DMA32 ((__force gfp_t)___GFP_DMA32)
|
2015-11-07 00:28:43 +00:00
|
|
|
#define __GFP_MOVABLE ((__force gfp_t)___GFP_MOVABLE) /* ZONE_MOVABLE allowed */
|
2009-06-16 22:32:46 +00:00
|
|
|
#define GFP_ZONEMASK (__GFP_DMA|__GFP_HIGHMEM|__GFP_DMA32|__GFP_MOVABLE)
|
2015-11-07 00:28:43 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
2015-11-07 00:28:43 +00:00
|
|
|
* Page mobility and placement hints
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
2015-11-07 00:28:43 +00:00
|
|
|
* These flags provide hints about how mobile the page is. Pages with similar
|
|
|
|
* mobility are placed within the same pageblocks to minimise problems due
|
|
|
|
* to external fragmentation.
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
2015-11-07 00:28:43 +00:00
|
|
|
* __GFP_MOVABLE (also a zone modifier) indicates that the page can be
|
|
|
|
* moved by page migration during memory compaction or can be reclaimed.
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
2015-11-07 00:28:43 +00:00
|
|
|
* __GFP_RECLAIMABLE is used for slab allocations that specify
|
|
|
|
* SLAB_RECLAIM_ACCOUNT and whose pages can be freed via shrinkers.
|
|
|
|
*
|
|
|
|
* __GFP_WRITE indicates the caller intends to dirty the page. Where possible,
|
|
|
|
* these pages will be spread between local zones to avoid all the dirty
|
|
|
|
* pages being in one zone (fair zone allocation policy).
|
2007-07-17 11:03:05 +00:00
|
|
|
*
|
2015-11-07 00:28:43 +00:00
|
|
|
* __GFP_HARDWALL enforces the cpuset memory allocation policy.
|
|
|
|
*
|
|
|
|
* __GFP_THISNODE forces the allocation to be satisified from the requested
|
|
|
|
* node with no fallbacks or placement policy enforcements.
|
2016-01-14 23:18:12 +00:00
|
|
|
*
|
|
|
|
* __GFP_ACCOUNT causes the allocation to be accounted to kmemcg (only relevant
|
|
|
|
* to kmem allocations).
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
2015-11-07 00:28:43 +00:00
|
|
|
#define __GFP_RECLAIMABLE ((__force gfp_t)___GFP_RECLAIMABLE)
|
|
|
|
#define __GFP_WRITE ((__force gfp_t)___GFP_WRITE)
|
|
|
|
#define __GFP_HARDWALL ((__force gfp_t)___GFP_HARDWALL)
|
|
|
|
#define __GFP_THISNODE ((__force gfp_t)___GFP_THISNODE)
|
2016-01-14 23:18:12 +00:00
|
|
|
#define __GFP_ACCOUNT ((__force gfp_t)___GFP_ACCOUNT)
|
2011-01-13 23:46:49 +00:00
|
|
|
|
2015-11-07 00:28:21 +00:00
|
|
|
/*
|
2015-11-07 00:28:43 +00:00
|
|
|
* Watermark modifiers -- controls access to emergency reserves
|
|
|
|
*
|
|
|
|
* __GFP_HIGH indicates that the caller is high-priority and that granting
|
|
|
|
* the request is necessary before the system can make forward progress.
|
|
|
|
* For example, creating an IO context to clean pages.
|
|
|
|
*
|
|
|
|
* __GFP_ATOMIC indicates that the caller cannot reclaim or sleep and is
|
|
|
|
* high priority. Users are typically interrupt handlers. This may be
|
|
|
|
* used in conjunction with __GFP_HIGH
|
|
|
|
*
|
|
|
|
* __GFP_MEMALLOC allows access to all memory. This should only be used when
|
|
|
|
* the caller guarantees the allocation will allow more memory to be freed
|
|
|
|
* very shortly e.g. process exiting or swapping. Users either should
|
|
|
|
* be the MM or co-ordinating closely with the VM (e.g. swap over NFS).
|
|
|
|
*
|
|
|
|
* __GFP_NOMEMALLOC is used to explicitly forbid access to emergency reserves.
|
|
|
|
* This takes precedence over the __GFP_MEMALLOC flag if both are set.
|
|
|
|
*
|
|
|
|
* __GFP_NOACCOUNT ignores the accounting for kmemcg limit enforcement.
|
2015-11-07 00:28:21 +00:00
|
|
|
*/
|
2015-11-07 00:28:43 +00:00
|
|
|
#define __GFP_ATOMIC ((__force gfp_t)___GFP_ATOMIC)
|
|
|
|
#define __GFP_HIGH ((__force gfp_t)___GFP_HIGH)
|
|
|
|
#define __GFP_MEMALLOC ((__force gfp_t)___GFP_MEMALLOC)
|
|
|
|
#define __GFP_NOMEMALLOC ((__force gfp_t)___GFP_NOMEMALLOC)
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Reclaim modifiers
|
|
|
|
*
|
|
|
|
* __GFP_IO can start physical IO.
|
|
|
|
*
|
|
|
|
* __GFP_FS can call down to the low-level FS. Clearing the flag avoids the
|
|
|
|
* allocator recursing into the filesystem which might already be holding
|
|
|
|
* locks.
|
|
|
|
*
|
|
|
|
* __GFP_DIRECT_RECLAIM indicates that the caller may enter direct reclaim.
|
|
|
|
* This flag can be cleared to avoid unnecessary delays when a fallback
|
|
|
|
* option is available.
|
|
|
|
*
|
|
|
|
* __GFP_KSWAPD_RECLAIM indicates that the caller wants to wake kswapd when
|
|
|
|
* the low watermark is reached and have it reclaim pages until the high
|
|
|
|
* watermark is reached. A caller may wish to clear this flag when fallback
|
|
|
|
* options are available and the reclaim is likely to disrupt the system. The
|
|
|
|
* canonical example is THP allocation where a fallback is cheap but
|
|
|
|
* reclaim/compaction may cause indirect stalls.
|
|
|
|
*
|
|
|
|
* __GFP_RECLAIM is shorthand to allow/forbid both direct and kswapd reclaim.
|
|
|
|
*
|
|
|
|
* __GFP_REPEAT: Try hard to allocate the memory, but the allocation attempt
|
|
|
|
* _might_ fail. This depends upon the particular VM implementation.
|
|
|
|
*
|
|
|
|
* __GFP_NOFAIL: The VM implementation _must_ retry infinitely: the caller
|
|
|
|
* cannot handle allocation failures. New users should be evaluated carefully
|
|
|
|
* (and the flag should be used only when there is no reasonable failure
|
|
|
|
* policy) 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 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.
|
|
|
|
*/
|
|
|
|
#define __GFP_IO ((__force gfp_t)___GFP_IO)
|
|
|
|
#define __GFP_FS ((__force gfp_t)___GFP_FS)
|
2015-11-07 00:28:21 +00:00
|
|
|
#define __GFP_DIRECT_RECLAIM ((__force gfp_t)___GFP_DIRECT_RECLAIM) /* Caller can reclaim */
|
|
|
|
#define __GFP_KSWAPD_RECLAIM ((__force gfp_t)___GFP_KSWAPD_RECLAIM) /* kswapd can wake */
|
2015-11-07 00:28:43 +00:00
|
|
|
#define __GFP_RECLAIM ((__force gfp_t)(___GFP_DIRECT_RECLAIM|___GFP_KSWAPD_RECLAIM))
|
|
|
|
#define __GFP_REPEAT ((__force gfp_t)___GFP_REPEAT)
|
|
|
|
#define __GFP_NOFAIL ((__force gfp_t)___GFP_NOFAIL)
|
|
|
|
#define __GFP_NORETRY ((__force gfp_t)___GFP_NORETRY)
|
2015-11-07 00:28:21 +00:00
|
|
|
|
kmemcheck: add mm functions
With kmemcheck enabled, the slab allocator needs to do this:
1. Tell kmemcheck to allocate the shadow memory which stores the status of
each byte in the allocation proper, e.g. whether it is initialized or
uninitialized.
2. Tell kmemcheck which parts of memory that should be marked uninitialized.
There are actually a few more states, such as "not yet allocated" and
"recently freed".
If a slab cache is set up using the SLAB_NOTRACK flag, it will never return
memory that can take page faults because of kmemcheck.
If a slab cache is NOT set up using the SLAB_NOTRACK flag, callers can still
request memory with the __GFP_NOTRACK flag. This does not prevent the page
faults from occuring, however, but marks the object in question as being
initialized so that no warnings will ever be produced for this object.
In addition to (and in contrast to) __GFP_NOTRACK, the
__GFP_NOTRACK_FALSE_POSITIVE flag indicates that the allocation should
not be tracked _because_ it would produce a false positive. Their values
are identical, but need not be so in the future (for example, we could now
enable/disable false positives with a config option).
Parts of this patch were contributed by Pekka Enberg but merged for
atomicity.
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
[rebased for mainline inclusion]
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
2008-05-31 13:56:17 +00:00
|
|
|
/*
|
2015-11-07 00:28:43 +00:00
|
|
|
* Action modifiers
|
|
|
|
*
|
|
|
|
* __GFP_COLD indicates that the caller does not expect to be used in the near
|
|
|
|
* future. Where possible, a cache-cold page will be returned.
|
|
|
|
*
|
|
|
|
* __GFP_NOWARN suppresses allocation failure reports.
|
|
|
|
*
|
|
|
|
* __GFP_COMP address compound page metadata.
|
|
|
|
*
|
|
|
|
* __GFP_ZERO returns a zeroed page on success.
|
|
|
|
*
|
|
|
|
* __GFP_NOTRACK avoids tracking with kmemcheck.
|
|
|
|
*
|
|
|
|
* __GFP_NOTRACK_FALSE_POSITIVE is an alias of __GFP_NOTRACK. It's a means of
|
|
|
|
* distinguishing in the source between false positives and allocations that
|
|
|
|
* cannot be supported (e.g. page tables).
|
|
|
|
*
|
|
|
|
* __GFP_OTHER_NODE is for allocations that are on a remote node but that
|
|
|
|
* should not be accounted for as a remote allocation in vmstat. A
|
|
|
|
* typical user would be khugepaged collapsing a huge page on a remote
|
|
|
|
* node.
|
kmemcheck: add mm functions
With kmemcheck enabled, the slab allocator needs to do this:
1. Tell kmemcheck to allocate the shadow memory which stores the status of
each byte in the allocation proper, e.g. whether it is initialized or
uninitialized.
2. Tell kmemcheck which parts of memory that should be marked uninitialized.
There are actually a few more states, such as "not yet allocated" and
"recently freed".
If a slab cache is set up using the SLAB_NOTRACK flag, it will never return
memory that can take page faults because of kmemcheck.
If a slab cache is NOT set up using the SLAB_NOTRACK flag, callers can still
request memory with the __GFP_NOTRACK flag. This does not prevent the page
faults from occuring, however, but marks the object in question as being
initialized so that no warnings will ever be produced for this object.
In addition to (and in contrast to) __GFP_NOTRACK, the
__GFP_NOTRACK_FALSE_POSITIVE flag indicates that the allocation should
not be tracked _because_ it would produce a false positive. Their values
are identical, but need not be so in the future (for example, we could now
enable/disable false positives with a config option).
Parts of this patch were contributed by Pekka Enberg but merged for
atomicity.
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
[rebased for mainline inclusion]
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
2008-05-31 13:56:17 +00:00
|
|
|
*/
|
2015-11-07 00:28:43 +00:00
|
|
|
#define __GFP_COLD ((__force gfp_t)___GFP_COLD)
|
|
|
|
#define __GFP_NOWARN ((__force gfp_t)___GFP_NOWARN)
|
|
|
|
#define __GFP_COMP ((__force gfp_t)___GFP_COMP)
|
|
|
|
#define __GFP_ZERO ((__force gfp_t)___GFP_ZERO)
|
|
|
|
#define __GFP_NOTRACK ((__force gfp_t)___GFP_NOTRACK)
|
kmemcheck: add mm functions
With kmemcheck enabled, the slab allocator needs to do this:
1. Tell kmemcheck to allocate the shadow memory which stores the status of
each byte in the allocation proper, e.g. whether it is initialized or
uninitialized.
2. Tell kmemcheck which parts of memory that should be marked uninitialized.
There are actually a few more states, such as "not yet allocated" and
"recently freed".
If a slab cache is set up using the SLAB_NOTRACK flag, it will never return
memory that can take page faults because of kmemcheck.
If a slab cache is NOT set up using the SLAB_NOTRACK flag, callers can still
request memory with the __GFP_NOTRACK flag. This does not prevent the page
faults from occuring, however, but marks the object in question as being
initialized so that no warnings will ever be produced for this object.
In addition to (and in contrast to) __GFP_NOTRACK, the
__GFP_NOTRACK_FALSE_POSITIVE flag indicates that the allocation should
not be tracked _because_ it would produce a false positive. Their values
are identical, but need not be so in the future (for example, we could now
enable/disable false positives with a config option).
Parts of this patch were contributed by Pekka Enberg but merged for
atomicity.
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
[rebased for mainline inclusion]
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
2008-05-31 13:56:17 +00:00
|
|
|
#define __GFP_NOTRACK_FALSE_POSITIVE (__GFP_NOTRACK)
|
2015-11-07 00:28:43 +00:00
|
|
|
#define __GFP_OTHER_NODE ((__force gfp_t)___GFP_OTHER_NODE)
|
kmemcheck: add mm functions
With kmemcheck enabled, the slab allocator needs to do this:
1. Tell kmemcheck to allocate the shadow memory which stores the status of
each byte in the allocation proper, e.g. whether it is initialized or
uninitialized.
2. Tell kmemcheck which parts of memory that should be marked uninitialized.
There are actually a few more states, such as "not yet allocated" and
"recently freed".
If a slab cache is set up using the SLAB_NOTRACK flag, it will never return
memory that can take page faults because of kmemcheck.
If a slab cache is NOT set up using the SLAB_NOTRACK flag, callers can still
request memory with the __GFP_NOTRACK flag. This does not prevent the page
faults from occuring, however, but marks the object in question as being
initialized so that no warnings will ever be produced for this object.
In addition to (and in contrast to) __GFP_NOTRACK, the
__GFP_NOTRACK_FALSE_POSITIVE flag indicates that the allocation should
not be tracked _because_ it would produce a false positive. Their values
are identical, but need not be so in the future (for example, we could now
enable/disable false positives with a config option).
Parts of this patch were contributed by Pekka Enberg but merged for
atomicity.
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
[rebased for mainline inclusion]
Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
2008-05-31 13:56:17 +00:00
|
|
|
|
2015-11-07 00:28:43 +00:00
|
|
|
/* Room for N __GFP_FOO bits */
|
|
|
|
#define __GFP_BITS_SHIFT 26
|
2005-10-21 06:55:38 +00:00
|
|
|
#define __GFP_BITS_MASK ((__force gfp_t)((1 << __GFP_BITS_SHIFT) - 1))
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2015-11-07 00:28:21 +00:00
|
|
|
/*
|
2015-11-07 00:28:43 +00:00
|
|
|
* Useful GFP flag combinations that are commonly used. It is recommended
|
|
|
|
* that subsystems start with one of these combinations and then set/clear
|
|
|
|
* __GFP_FOO flags as necessary.
|
|
|
|
*
|
|
|
|
* GFP_ATOMIC users can not sleep and need the allocation to succeed. A lower
|
|
|
|
* watermark is applied to allow access to "atomic reserves"
|
|
|
|
*
|
|
|
|
* GFP_KERNEL is typical for kernel-internal allocations. The caller requires
|
|
|
|
* ZONE_NORMAL or a lower zone for direct access but can direct reclaim.
|
|
|
|
*
|
2016-01-14 23:18:12 +00:00
|
|
|
* GFP_KERNEL_ACCOUNT is the same as GFP_KERNEL, except the allocation is
|
|
|
|
* accounted to kmemcg.
|
|
|
|
*
|
2015-11-07 00:28:43 +00:00
|
|
|
* GFP_NOWAIT is for kernel allocations that should not stall for direct
|
|
|
|
* reclaim, start physical IO or use any filesystem callback.
|
|
|
|
*
|
|
|
|
* GFP_NOIO will use direct reclaim to discard clean pages or slab pages
|
|
|
|
* that do not require the starting of any physical IO.
|
|
|
|
*
|
|
|
|
* GFP_NOFS will use direct reclaim but will not use any filesystem interfaces.
|
|
|
|
*
|
|
|
|
* GFP_USER is for userspace allocations that also need to be directly
|
|
|
|
* accessibly by the kernel or hardware. It is typically used by hardware
|
|
|
|
* for buffers that are mapped to userspace (e.g. graphics) that hardware
|
|
|
|
* still must DMA to. cpuset limits are enforced for these allocations.
|
|
|
|
*
|
|
|
|
* GFP_DMA exists for historical reasons and should be avoided where possible.
|
|
|
|
* The flags indicates that the caller requires that the lowest zone be
|
|
|
|
* used (ZONE_DMA or 16M on x86-64). Ideally, this would be removed but
|
|
|
|
* it would require careful auditing as some users really require it and
|
|
|
|
* others use the flag to avoid lowmem reserves in ZONE_DMA and treat the
|
|
|
|
* lowest zone as a type of emergency reserve.
|
|
|
|
*
|
|
|
|
* GFP_DMA32 is similar to GFP_DMA except that the caller requires a 32-bit
|
|
|
|
* address.
|
|
|
|
*
|
|
|
|
* GFP_HIGHUSER is for userspace allocations that may be mapped to userspace,
|
|
|
|
* do not need to be directly accessible by the kernel but that cannot
|
|
|
|
* move once in use. An example may be a hardware allocation that maps
|
|
|
|
* data directly into userspace but has no addressing limitations.
|
|
|
|
*
|
|
|
|
* GFP_HIGHUSER_MOVABLE is for userspace allocations that the kernel does not
|
|
|
|
* need direct access to but can use kmap() when access is required. They
|
|
|
|
* are expected to be movable via page reclaim or page migration. Typically,
|
|
|
|
* pages on the LRU would also be allocated with GFP_HIGHUSER_MOVABLE.
|
|
|
|
*
|
|
|
|
* GFP_TRANSHUGE is used for THP allocations. They are compound allocations
|
|
|
|
* that will fail quickly if memory is not available and will not wake
|
|
|
|
* kswapd on failure.
|
2015-11-07 00:28:21 +00:00
|
|
|
*/
|
|
|
|
#define GFP_ATOMIC (__GFP_HIGH|__GFP_ATOMIC|__GFP_KSWAPD_RECLAIM)
|
2015-11-07 00:28:43 +00:00
|
|
|
#define GFP_KERNEL (__GFP_RECLAIM | __GFP_IO | __GFP_FS)
|
2016-01-14 23:18:12 +00:00
|
|
|
#define GFP_KERNEL_ACCOUNT (GFP_KERNEL | __GFP_ACCOUNT)
|
2015-11-07 00:28:21 +00:00
|
|
|
#define GFP_NOWAIT (__GFP_KSWAPD_RECLAIM)
|
2015-11-07 00:28:28 +00:00
|
|
|
#define GFP_NOIO (__GFP_RECLAIM)
|
|
|
|
#define GFP_NOFS (__GFP_RECLAIM | __GFP_IO)
|
|
|
|
#define GFP_TEMPORARY (__GFP_RECLAIM | __GFP_IO | __GFP_FS | \
|
2007-10-16 08:25:52 +00:00
|
|
|
__GFP_RECLAIMABLE)
|
2015-11-07 00:28:28 +00:00
|
|
|
#define GFP_USER (__GFP_RECLAIM | __GFP_IO | __GFP_FS | __GFP_HARDWALL)
|
2015-11-07 00:28:43 +00:00
|
|
|
#define GFP_DMA __GFP_DMA
|
|
|
|
#define GFP_DMA32 __GFP_DMA32
|
2014-12-13 00:55:43 +00:00
|
|
|
#define GFP_HIGHUSER (GFP_USER | __GFP_HIGHMEM)
|
|
|
|
#define GFP_HIGHUSER_MOVABLE (GFP_HIGHUSER | __GFP_MOVABLE)
|
2015-11-07 00:28:21 +00:00
|
|
|
#define GFP_TRANSHUGE ((GFP_HIGHUSER_MOVABLE | __GFP_COMP | \
|
|
|
|
__GFP_NOMEMALLOC | __GFP_NORETRY | __GFP_NOWARN) & \
|
|
|
|
~__GFP_KSWAPD_RECLAIM)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2015-11-07 00:28:43 +00:00
|
|
|
/* Convert GFP flags to their corresponding migrate type */
|
2007-10-16 08:25:52 +00:00
|
|
|
#define GFP_MOVABLE_MASK (__GFP_RECLAIMABLE|__GFP_MOVABLE)
|
2015-11-07 00:28:18 +00:00
|
|
|
#define GFP_MOVABLE_SHIFT 3
|
2007-10-16 08:25:41 +00:00
|
|
|
|
2014-10-09 22:27:25 +00:00
|
|
|
static inline int gfpflags_to_migratetype(const gfp_t gfp_flags)
|
Print out statistics in relation to fragmentation avoidance to /proc/pagetypeinfo
This patch provides fragmentation avoidance statistics via /proc/pagetypeinfo.
The information is collected only on request so there is no runtime overhead.
The statistics are in three parts:
The first part prints information on the size of blocks that pages are
being grouped on and looks like
Page block order: 10
Pages per block: 1024
The second part is a more detailed version of /proc/buddyinfo and looks like
Free pages count per migrate type at order 0 1 2 3 4 5 6 7 8 9 10
Node 0, zone DMA, type Unmovable 0 0 0 0 0 0 0 0 0 0 0
Node 0, zone DMA, type Reclaimable 1 0 0 0 0 0 0 0 0 0 0
Node 0, zone DMA, type Movable 0 0 0 0 0 0 0 0 0 0 0
Node 0, zone DMA, type Reserve 0 4 4 0 0 0 0 1 0 1 0
Node 0, zone Normal, type Unmovable 111 8 4 4 2 3 1 0 0 0 0
Node 0, zone Normal, type Reclaimable 293 89 8 0 0 0 0 0 0 0 0
Node 0, zone Normal, type Movable 1 6 13 9 7 6 3 0 0 0 0
Node 0, zone Normal, type Reserve 0 0 0 0 0 0 0 0 0 0 4
The third part looks like
Number of blocks type Unmovable Reclaimable Movable Reserve
Node 0, zone DMA 0 1 2 1
Node 0, zone Normal 3 17 94 4
To walk the zones within a node with interrupts disabled, walk_zones_in_node()
is introduced and shared between /proc/buddyinfo, /proc/zoneinfo and
/proc/pagetypeinfo to reduce code duplication. It seems specific to what
vmstat.c requires but could be broken out as a general utility function in
mmzone.c if there were other other potential users.
Signed-off-by: Mel Gorman <mel@csn.ul.ie>
Acked-by: Andy Whitcroft <apw@shadowen.org>
Acked-by: Christoph Lameter <clameter@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-10-16 08:26:02 +00:00
|
|
|
{
|
2015-11-07 00:28:18 +00:00
|
|
|
VM_WARN_ON((gfp_flags & GFP_MOVABLE_MASK) == GFP_MOVABLE_MASK);
|
|
|
|
BUILD_BUG_ON((1UL << GFP_MOVABLE_SHIFT) != ___GFP_MOVABLE);
|
|
|
|
BUILD_BUG_ON((___GFP_MOVABLE >> GFP_MOVABLE_SHIFT) != MIGRATE_MOVABLE);
|
Print out statistics in relation to fragmentation avoidance to /proc/pagetypeinfo
This patch provides fragmentation avoidance statistics via /proc/pagetypeinfo.
The information is collected only on request so there is no runtime overhead.
The statistics are in three parts:
The first part prints information on the size of blocks that pages are
being grouped on and looks like
Page block order: 10
Pages per block: 1024
The second part is a more detailed version of /proc/buddyinfo and looks like
Free pages count per migrate type at order 0 1 2 3 4 5 6 7 8 9 10
Node 0, zone DMA, type Unmovable 0 0 0 0 0 0 0 0 0 0 0
Node 0, zone DMA, type Reclaimable 1 0 0 0 0 0 0 0 0 0 0
Node 0, zone DMA, type Movable 0 0 0 0 0 0 0 0 0 0 0
Node 0, zone DMA, type Reserve 0 4 4 0 0 0 0 1 0 1 0
Node 0, zone Normal, type Unmovable 111 8 4 4 2 3 1 0 0 0 0
Node 0, zone Normal, type Reclaimable 293 89 8 0 0 0 0 0 0 0 0
Node 0, zone Normal, type Movable 1 6 13 9 7 6 3 0 0 0 0
Node 0, zone Normal, type Reserve 0 0 0 0 0 0 0 0 0 0 4
The third part looks like
Number of blocks type Unmovable Reclaimable Movable Reserve
Node 0, zone DMA 0 1 2 1
Node 0, zone Normal 3 17 94 4
To walk the zones within a node with interrupts disabled, walk_zones_in_node()
is introduced and shared between /proc/buddyinfo, /proc/zoneinfo and
/proc/pagetypeinfo to reduce code duplication. It seems specific to what
vmstat.c requires but could be broken out as a general utility function in
mmzone.c if there were other other potential users.
Signed-off-by: Mel Gorman <mel@csn.ul.ie>
Acked-by: Andy Whitcroft <apw@shadowen.org>
Acked-by: Christoph Lameter <clameter@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-10-16 08:26:02 +00:00
|
|
|
|
|
|
|
if (unlikely(page_group_by_mobility_disabled))
|
|
|
|
return MIGRATE_UNMOVABLE;
|
|
|
|
|
|
|
|
/* Group based on mobility */
|
2015-11-07 00:28:18 +00:00
|
|
|
return (gfp_flags & GFP_MOVABLE_MASK) >> GFP_MOVABLE_SHIFT;
|
Print out statistics in relation to fragmentation avoidance to /proc/pagetypeinfo
This patch provides fragmentation avoidance statistics via /proc/pagetypeinfo.
The information is collected only on request so there is no runtime overhead.
The statistics are in three parts:
The first part prints information on the size of blocks that pages are
being grouped on and looks like
Page block order: 10
Pages per block: 1024
The second part is a more detailed version of /proc/buddyinfo and looks like
Free pages count per migrate type at order 0 1 2 3 4 5 6 7 8 9 10
Node 0, zone DMA, type Unmovable 0 0 0 0 0 0 0 0 0 0 0
Node 0, zone DMA, type Reclaimable 1 0 0 0 0 0 0 0 0 0 0
Node 0, zone DMA, type Movable 0 0 0 0 0 0 0 0 0 0 0
Node 0, zone DMA, type Reserve 0 4 4 0 0 0 0 1 0 1 0
Node 0, zone Normal, type Unmovable 111 8 4 4 2 3 1 0 0 0 0
Node 0, zone Normal, type Reclaimable 293 89 8 0 0 0 0 0 0 0 0
Node 0, zone Normal, type Movable 1 6 13 9 7 6 3 0 0 0 0
Node 0, zone Normal, type Reserve 0 0 0 0 0 0 0 0 0 0 4
The third part looks like
Number of blocks type Unmovable Reclaimable Movable Reserve
Node 0, zone DMA 0 1 2 1
Node 0, zone Normal 3 17 94 4
To walk the zones within a node with interrupts disabled, walk_zones_in_node()
is introduced and shared between /proc/buddyinfo, /proc/zoneinfo and
/proc/pagetypeinfo to reduce code duplication. It seems specific to what
vmstat.c requires but could be broken out as a general utility function in
mmzone.c if there were other other potential users.
Signed-off-by: Mel Gorman <mel@csn.ul.ie>
Acked-by: Andy Whitcroft <apw@shadowen.org>
Acked-by: Christoph Lameter <clameter@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-10-16 08:26:02 +00:00
|
|
|
}
|
2015-11-07 00:28:43 +00:00
|
|
|
#undef GFP_MOVABLE_MASK
|
|
|
|
#undef GFP_MOVABLE_SHIFT
|
2005-11-05 16:25:53 +00:00
|
|
|
|
2015-11-07 00:28:21 +00:00
|
|
|
static inline bool gfpflags_allow_blocking(const gfp_t gfp_flags)
|
|
|
|
{
|
2016-01-14 23:22:10 +00:00
|
|
|
return !!(gfp_flags & __GFP_DIRECT_RECLAIM);
|
2015-11-07 00:28:21 +00:00
|
|
|
}
|
|
|
|
|
2009-06-16 22:32:46 +00:00
|
|
|
#ifdef CONFIG_HIGHMEM
|
|
|
|
#define OPT_ZONE_HIGHMEM ZONE_HIGHMEM
|
|
|
|
#else
|
|
|
|
#define OPT_ZONE_HIGHMEM ZONE_NORMAL
|
|
|
|
#endif
|
|
|
|
|
2007-02-10 09:43:10 +00:00
|
|
|
#ifdef CONFIG_ZONE_DMA
|
2009-06-16 22:32:46 +00:00
|
|
|
#define OPT_ZONE_DMA ZONE_DMA
|
|
|
|
#else
|
|
|
|
#define OPT_ZONE_DMA ZONE_NORMAL
|
2007-02-10 09:43:10 +00:00
|
|
|
#endif
|
2009-06-16 22:32:46 +00:00
|
|
|
|
2006-09-26 06:31:17 +00:00
|
|
|
#ifdef CONFIG_ZONE_DMA32
|
2009-06-16 22:32:46 +00:00
|
|
|
#define OPT_ZONE_DMA32 ZONE_DMA32
|
|
|
|
#else
|
|
|
|
#define OPT_ZONE_DMA32 ZONE_NORMAL
|
2006-09-26 06:31:17 +00:00
|
|
|
#endif
|
2009-06-16 22:32:46 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* GFP_ZONE_TABLE is a word size bitstring that is used for looking up the
|
|
|
|
* zone to use given the lowest 4 bits of gfp_t. Entries are ZONE_SHIFT long
|
|
|
|
* and there are 16 of them to cover all possible combinations of
|
2010-05-24 21:32:44 +00:00
|
|
|
* __GFP_DMA, __GFP_DMA32, __GFP_MOVABLE and __GFP_HIGHMEM.
|
2009-06-16 22:32:46 +00:00
|
|
|
*
|
|
|
|
* The zone fallback order is MOVABLE=>HIGHMEM=>NORMAL=>DMA32=>DMA.
|
|
|
|
* But GFP_MOVABLE is not only a zone specifier but also an allocation
|
|
|
|
* policy. Therefore __GFP_MOVABLE plus another zone selector is valid.
|
2010-05-24 21:32:44 +00:00
|
|
|
* Only 1 bit of the lowest 3 bits (DMA,DMA32,HIGHMEM) can be set to "1".
|
2009-06-16 22:32:46 +00:00
|
|
|
*
|
|
|
|
* bit result
|
|
|
|
* =================
|
|
|
|
* 0x0 => NORMAL
|
|
|
|
* 0x1 => DMA or NORMAL
|
|
|
|
* 0x2 => HIGHMEM or NORMAL
|
|
|
|
* 0x3 => BAD (DMA+HIGHMEM)
|
|
|
|
* 0x4 => DMA32 or DMA or NORMAL
|
|
|
|
* 0x5 => BAD (DMA+DMA32)
|
|
|
|
* 0x6 => BAD (HIGHMEM+DMA32)
|
|
|
|
* 0x7 => BAD (HIGHMEM+DMA32+DMA)
|
|
|
|
* 0x8 => NORMAL (MOVABLE+0)
|
|
|
|
* 0x9 => DMA or NORMAL (MOVABLE+DMA)
|
|
|
|
* 0xa => MOVABLE (Movable is valid only if HIGHMEM is set too)
|
|
|
|
* 0xb => BAD (MOVABLE+HIGHMEM+DMA)
|
2013-07-08 23:00:02 +00:00
|
|
|
* 0xc => DMA32 (MOVABLE+DMA32)
|
2009-06-16 22:32:46 +00:00
|
|
|
* 0xd => BAD (MOVABLE+DMA32+DMA)
|
|
|
|
* 0xe => BAD (MOVABLE+DMA32+HIGHMEM)
|
|
|
|
* 0xf => BAD (MOVABLE+DMA32+HIGHMEM+DMA)
|
|
|
|
*
|
|
|
|
* ZONES_SHIFT must be <= 2 on 32 bit platforms.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#if 16 * ZONES_SHIFT > BITS_PER_LONG
|
|
|
|
#error ZONES_SHIFT too large to create GFP_ZONE_TABLE integer
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#define GFP_ZONE_TABLE ( \
|
2010-10-26 21:22:04 +00:00
|
|
|
(ZONE_NORMAL << 0 * ZONES_SHIFT) \
|
|
|
|
| (OPT_ZONE_DMA << ___GFP_DMA * ZONES_SHIFT) \
|
|
|
|
| (OPT_ZONE_HIGHMEM << ___GFP_HIGHMEM * ZONES_SHIFT) \
|
|
|
|
| (OPT_ZONE_DMA32 << ___GFP_DMA32 * ZONES_SHIFT) \
|
|
|
|
| (ZONE_NORMAL << ___GFP_MOVABLE * ZONES_SHIFT) \
|
|
|
|
| (OPT_ZONE_DMA << (___GFP_MOVABLE | ___GFP_DMA) * ZONES_SHIFT) \
|
|
|
|
| (ZONE_MOVABLE << (___GFP_MOVABLE | ___GFP_HIGHMEM) * ZONES_SHIFT) \
|
|
|
|
| (OPT_ZONE_DMA32 << (___GFP_MOVABLE | ___GFP_DMA32) * ZONES_SHIFT) \
|
2009-06-16 22:32:46 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
/*
|
2010-05-24 21:32:44 +00:00
|
|
|
* GFP_ZONE_BAD is a bitmap for all combinations of __GFP_DMA, __GFP_DMA32
|
2009-06-16 22:32:46 +00:00
|
|
|
* __GFP_HIGHMEM and __GFP_MOVABLE that are not permitted. One flag per
|
|
|
|
* entry starting with bit 0. Bit is set if the combination is not
|
|
|
|
* allowed.
|
|
|
|
*/
|
|
|
|
#define GFP_ZONE_BAD ( \
|
2010-10-26 21:22:04 +00:00
|
|
|
1 << (___GFP_DMA | ___GFP_HIGHMEM) \
|
|
|
|
| 1 << (___GFP_DMA | ___GFP_DMA32) \
|
|
|
|
| 1 << (___GFP_DMA32 | ___GFP_HIGHMEM) \
|
|
|
|
| 1 << (___GFP_DMA | ___GFP_DMA32 | ___GFP_HIGHMEM) \
|
|
|
|
| 1 << (___GFP_MOVABLE | ___GFP_HIGHMEM | ___GFP_DMA) \
|
|
|
|
| 1 << (___GFP_MOVABLE | ___GFP_DMA32 | ___GFP_DMA) \
|
|
|
|
| 1 << (___GFP_MOVABLE | ___GFP_DMA32 | ___GFP_HIGHMEM) \
|
|
|
|
| 1 << (___GFP_MOVABLE | ___GFP_DMA32 | ___GFP_DMA | ___GFP_HIGHMEM) \
|
2009-06-16 22:32:46 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
static inline enum zone_type gfp_zone(gfp_t flags)
|
|
|
|
{
|
|
|
|
enum zone_type z;
|
2010-10-26 21:22:04 +00:00
|
|
|
int bit = (__force int) (flags & GFP_ZONEMASK);
|
2009-06-16 22:32:46 +00:00
|
|
|
|
|
|
|
z = (GFP_ZONE_TABLE >> (bit * ZONES_SHIFT)) &
|
|
|
|
((1 << ZONES_SHIFT) - 1);
|
2011-05-25 00:11:42 +00:00
|
|
|
VM_BUG_ON((GFP_ZONE_BAD >> bit) & 1);
|
2009-06-16 22:32:46 +00:00
|
|
|
return z;
|
2006-09-26 06:31:17 +00:00
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* There is only one page-allocator function, and two main namespaces to
|
|
|
|
* it. The alloc_page*() variants return 'struct page *' and as such
|
|
|
|
* can allocate highmem pages, the *get*page*() variants return
|
|
|
|
* virtual kernel addresses to the allocated page(s).
|
|
|
|
*/
|
|
|
|
|
2008-04-28 09:12:16 +00:00
|
|
|
static inline int gfp_zonelist(gfp_t flags)
|
|
|
|
{
|
2016-01-14 23:19:00 +00:00
|
|
|
#ifdef CONFIG_NUMA
|
|
|
|
if (unlikely(flags & __GFP_THISNODE))
|
|
|
|
return ZONELIST_NOFALLBACK;
|
|
|
|
#endif
|
|
|
|
return ZONELIST_FALLBACK;
|
2008-04-28 09:12:16 +00:00
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
/*
|
|
|
|
* We get the zone list from the current node and the gfp_mask.
|
|
|
|
* This zone list contains a maximum of MAXNODES*MAX_NR_ZONES zones.
|
2008-04-28 09:12:16 +00:00
|
|
|
* There are two zonelists per node, one for all zones with memory and
|
|
|
|
* one containing just zones from the node the zonelist belongs to.
|
2005-04-16 22:20:36 +00:00
|
|
|
*
|
|
|
|
* For the normal case of non-DISCONTIGMEM systems the NODE_DATA() gets
|
|
|
|
* optimized to &contig_page_data at compile-time.
|
|
|
|
*/
|
2008-04-28 09:12:14 +00:00
|
|
|
static inline struct zonelist *node_zonelist(int nid, gfp_t flags)
|
|
|
|
{
|
2008-04-28 09:12:16 +00:00
|
|
|
return NODE_DATA(nid)->node_zonelists + gfp_zonelist(flags);
|
2008-04-28 09:12:14 +00:00
|
|
|
}
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
#ifndef HAVE_ARCH_FREE_PAGE
|
|
|
|
static inline void arch_free_page(struct page *page, int order) { }
|
|
|
|
#endif
|
2006-12-07 04:32:00 +00:00
|
|
|
#ifndef HAVE_ARCH_ALLOC_PAGE
|
|
|
|
static inline void arch_alloc_page(struct page *page, int order) { }
|
|
|
|
#endif
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-07-24 04:27:01 +00:00
|
|
|
struct page *
|
2009-06-16 22:31:52 +00:00
|
|
|
__alloc_pages_nodemask(gfp_t gfp_mask, unsigned int order,
|
2008-07-24 04:27:01 +00:00
|
|
|
struct zonelist *zonelist, nodemask_t *nodemask);
|
|
|
|
|
|
|
|
static inline struct page *
|
|
|
|
__alloc_pages(gfp_t gfp_mask, unsigned int order,
|
|
|
|
struct zonelist *zonelist)
|
|
|
|
{
|
2009-06-16 22:31:52 +00:00
|
|
|
return __alloc_pages_nodemask(gfp_mask, order, zonelist, NULL);
|
2008-07-24 04:27:01 +00:00
|
|
|
}
|
|
|
|
|
mm: rename alloc_pages_exact_node() to __alloc_pages_node()
alloc_pages_exact_node() was introduced in commit 6484eb3e2a81 ("page
allocator: do not check NUMA node ID when the caller knows the node is
valid") as an optimized variant of alloc_pages_node(), that doesn't
fallback to current node for nid == NUMA_NO_NODE. Unfortunately the
name of the function can easily suggest that the allocation is
restricted to the given node and fails otherwise. In truth, the node is
only preferred, unless __GFP_THISNODE is passed among the gfp flags.
The misleading name has lead to mistakes in the past, see for example
commits 5265047ac301 ("mm, thp: really limit transparent hugepage
allocation to local node") and b360edb43f8e ("mm, mempolicy:
migrate_to_node should only migrate to node").
Another issue with the name is that there's a family of
alloc_pages_exact*() functions where 'exact' means exact size (instead
of page order), which leads to more confusion.
To prevent further mistakes, this patch effectively renames
alloc_pages_exact_node() to __alloc_pages_node() to better convey that
it's an optimized variant of alloc_pages_node() not intended for general
usage. Both functions get described in comments.
It has been also considered to really provide a convenience function for
allocations restricted to a node, but the major opinion seems to be that
__GFP_THISNODE already provides that functionality and we shouldn't
duplicate the API needlessly. The number of users would be small
anyway.
Existing callers of alloc_pages_exact_node() are simply converted to
call __alloc_pages_node(), with the exception of sba_alloc_coherent()
which open-codes the check for NUMA_NO_NODE, so it is converted to use
alloc_pages_node() instead. This means it no longer performs some
VM_BUG_ON checks, and since the current check for nid in
alloc_pages_node() uses a 'nid < 0' comparison (which includes
NUMA_NO_NODE), it may hide wrong values which would be previously
exposed.
Both differences will be rectified by the next patch.
To sum up, this patch makes no functional changes, except temporarily
hiding potentially buggy callers. Restricting the checks in
alloc_pages_node() is left for the next patch which can in turn expose
more existing buggy callers.
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Robin Holt <robinmholt@gmail.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Acked-by: Christoph Lameter <cl@linux.com>
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
Cc: Mel Gorman <mgorman@suse.de>
Cc: David Rientjes <rientjes@google.com>
Cc: Greg Thelen <gthelen@google.com>
Cc: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Cc: Pekka Enberg <penberg@kernel.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Gleb Natapov <gleb@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Cliff Whickman <cpw@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2015-09-08 22:03:50 +00:00
|
|
|
/*
|
|
|
|
* Allocate pages, preferring the node given as nid. The node must be valid and
|
|
|
|
* online. For more general interface, see alloc_pages_node().
|
|
|
|
*/
|
|
|
|
static inline struct page *
|
|
|
|
__alloc_pages_node(int nid, gfp_t gfp_mask, unsigned int order)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
2015-09-08 22:03:53 +00:00
|
|
|
VM_BUG_ON(nid < 0 || nid >= MAX_NUMNODES);
|
|
|
|
VM_WARN_ON(!node_online(nid));
|
2006-01-11 21:43:45 +00:00
|
|
|
|
2008-04-28 09:12:14 +00:00
|
|
|
return __alloc_pages(gfp_mask, order, node_zonelist(nid, gfp_mask));
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
|
mm: rename alloc_pages_exact_node() to __alloc_pages_node()
alloc_pages_exact_node() was introduced in commit 6484eb3e2a81 ("page
allocator: do not check NUMA node ID when the caller knows the node is
valid") as an optimized variant of alloc_pages_node(), that doesn't
fallback to current node for nid == NUMA_NO_NODE. Unfortunately the
name of the function can easily suggest that the allocation is
restricted to the given node and fails otherwise. In truth, the node is
only preferred, unless __GFP_THISNODE is passed among the gfp flags.
The misleading name has lead to mistakes in the past, see for example
commits 5265047ac301 ("mm, thp: really limit transparent hugepage
allocation to local node") and b360edb43f8e ("mm, mempolicy:
migrate_to_node should only migrate to node").
Another issue with the name is that there's a family of
alloc_pages_exact*() functions where 'exact' means exact size (instead
of page order), which leads to more confusion.
To prevent further mistakes, this patch effectively renames
alloc_pages_exact_node() to __alloc_pages_node() to better convey that
it's an optimized variant of alloc_pages_node() not intended for general
usage. Both functions get described in comments.
It has been also considered to really provide a convenience function for
allocations restricted to a node, but the major opinion seems to be that
__GFP_THISNODE already provides that functionality and we shouldn't
duplicate the API needlessly. The number of users would be small
anyway.
Existing callers of alloc_pages_exact_node() are simply converted to
call __alloc_pages_node(), with the exception of sba_alloc_coherent()
which open-codes the check for NUMA_NO_NODE, so it is converted to use
alloc_pages_node() instead. This means it no longer performs some
VM_BUG_ON checks, and since the current check for nid in
alloc_pages_node() uses a 'nid < 0' comparison (which includes
NUMA_NO_NODE), it may hide wrong values which would be previously
exposed.
Both differences will be rectified by the next patch.
To sum up, this patch makes no functional changes, except temporarily
hiding potentially buggy callers. Restricting the checks in
alloc_pages_node() is left for the next patch which can in turn expose
more existing buggy callers.
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Robin Holt <robinmholt@gmail.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Acked-by: Christoph Lameter <cl@linux.com>
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
Cc: Mel Gorman <mgorman@suse.de>
Cc: David Rientjes <rientjes@google.com>
Cc: Greg Thelen <gthelen@google.com>
Cc: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Cc: Pekka Enberg <penberg@kernel.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Gleb Natapov <gleb@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Cliff Whickman <cpw@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2015-09-08 22:03:50 +00:00
|
|
|
/*
|
|
|
|
* Allocate pages, preferring the node given as nid. When nid == NUMA_NO_NODE,
|
2015-09-08 22:03:56 +00:00
|
|
|
* prefer the current CPU's closest node. Otherwise node must be valid and
|
|
|
|
* online.
|
mm: rename alloc_pages_exact_node() to __alloc_pages_node()
alloc_pages_exact_node() was introduced in commit 6484eb3e2a81 ("page
allocator: do not check NUMA node ID when the caller knows the node is
valid") as an optimized variant of alloc_pages_node(), that doesn't
fallback to current node for nid == NUMA_NO_NODE. Unfortunately the
name of the function can easily suggest that the allocation is
restricted to the given node and fails otherwise. In truth, the node is
only preferred, unless __GFP_THISNODE is passed among the gfp flags.
The misleading name has lead to mistakes in the past, see for example
commits 5265047ac301 ("mm, thp: really limit transparent hugepage
allocation to local node") and b360edb43f8e ("mm, mempolicy:
migrate_to_node should only migrate to node").
Another issue with the name is that there's a family of
alloc_pages_exact*() functions where 'exact' means exact size (instead
of page order), which leads to more confusion.
To prevent further mistakes, this patch effectively renames
alloc_pages_exact_node() to __alloc_pages_node() to better convey that
it's an optimized variant of alloc_pages_node() not intended for general
usage. Both functions get described in comments.
It has been also considered to really provide a convenience function for
allocations restricted to a node, but the major opinion seems to be that
__GFP_THISNODE already provides that functionality and we shouldn't
duplicate the API needlessly. The number of users would be small
anyway.
Existing callers of alloc_pages_exact_node() are simply converted to
call __alloc_pages_node(), with the exception of sba_alloc_coherent()
which open-codes the check for NUMA_NO_NODE, so it is converted to use
alloc_pages_node() instead. This means it no longer performs some
VM_BUG_ON checks, and since the current check for nid in
alloc_pages_node() uses a 'nid < 0' comparison (which includes
NUMA_NO_NODE), it may hide wrong values which would be previously
exposed.
Both differences will be rectified by the next patch.
To sum up, this patch makes no functional changes, except temporarily
hiding potentially buggy callers. Restricting the checks in
alloc_pages_node() is left for the next patch which can in turn expose
more existing buggy callers.
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Robin Holt <robinmholt@gmail.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Acked-by: Christoph Lameter <cl@linux.com>
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
Cc: Mel Gorman <mgorman@suse.de>
Cc: David Rientjes <rientjes@google.com>
Cc: Greg Thelen <gthelen@google.com>
Cc: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Cc: Pekka Enberg <penberg@kernel.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Gleb Natapov <gleb@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Cliff Whickman <cpw@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2015-09-08 22:03:50 +00:00
|
|
|
*/
|
|
|
|
static inline struct page *alloc_pages_node(int nid, gfp_t gfp_mask,
|
2009-06-16 22:31:54 +00:00
|
|
|
unsigned int order)
|
|
|
|
{
|
2015-09-08 22:03:53 +00:00
|
|
|
if (nid == NUMA_NO_NODE)
|
2015-09-08 22:03:56 +00:00
|
|
|
nid = numa_mem_id();
|
2009-06-16 22:31:54 +00:00
|
|
|
|
2015-09-08 22:03:53 +00:00
|
|
|
return __alloc_pages_node(nid, gfp_mask, order);
|
2009-06-16 22:31:54 +00:00
|
|
|
}
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#ifdef CONFIG_NUMA
|
2005-10-07 06:46:04 +00:00
|
|
|
extern struct page *alloc_pages_current(gfp_t gfp_mask, unsigned order);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
static inline struct page *
|
2005-10-07 06:46:04 +00:00
|
|
|
alloc_pages(gfp_t gfp_mask, unsigned int order)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
|
|
|
return alloc_pages_current(gfp_mask, order);
|
|
|
|
}
|
2011-01-13 23:47:05 +00:00
|
|
|
extern struct page *alloc_pages_vma(gfp_t gfp_mask, int order,
|
2011-03-05 01:36:29 +00:00
|
|
|
struct vm_area_struct *vma, unsigned long addr,
|
2015-02-11 23:27:15 +00:00
|
|
|
int node, bool hugepage);
|
|
|
|
#define alloc_hugepage_vma(gfp_mask, vma, addr, order) \
|
|
|
|
alloc_pages_vma(gfp_mask, order, vma, addr, numa_node_id(), true)
|
2005-04-16 22:20:36 +00:00
|
|
|
#else
|
|
|
|
#define alloc_pages(gfp_mask, order) \
|
|
|
|
alloc_pages_node(numa_node_id(), gfp_mask, order)
|
2015-02-11 23:27:15 +00:00
|
|
|
#define alloc_pages_vma(gfp_mask, order, vma, addr, node, false)\
|
2011-01-13 23:47:05 +00:00
|
|
|
alloc_pages(gfp_mask, order)
|
2015-02-11 23:27:12 +00:00
|
|
|
#define alloc_hugepage_vma(gfp_mask, vma, addr, order) \
|
|
|
|
alloc_pages(gfp_mask, order)
|
2005-04-16 22:20:36 +00:00
|
|
|
#endif
|
|
|
|
#define alloc_page(gfp_mask) alloc_pages(gfp_mask, 0)
|
2011-03-05 01:36:29 +00:00
|
|
|
#define alloc_page_vma(gfp_mask, vma, addr) \
|
2015-02-11 23:27:15 +00:00
|
|
|
alloc_pages_vma(gfp_mask, 0, vma, addr, numa_node_id(), false)
|
2011-03-05 01:36:30 +00:00
|
|
|
#define alloc_page_vma_node(gfp_mask, vma, addr, node) \
|
2015-02-11 23:27:15 +00:00
|
|
|
alloc_pages_vma(gfp_mask, 0, vma, addr, node, false)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2014-06-04 23:06:39 +00:00
|
|
|
extern struct page *alloc_kmem_pages(gfp_t gfp_mask, unsigned int order);
|
|
|
|
extern struct page *alloc_kmem_pages_node(int nid, gfp_t gfp_mask,
|
|
|
|
unsigned int order);
|
|
|
|
|
2008-02-13 23:03:15 +00:00
|
|
|
extern unsigned long __get_free_pages(gfp_t gfp_mask, unsigned int order);
|
|
|
|
extern unsigned long get_zeroed_page(gfp_t gfp_mask);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-07-24 04:28:11 +00:00
|
|
|
void *alloc_pages_exact(size_t size, gfp_t gfp_mask);
|
|
|
|
void free_pages_exact(void *virt, size_t size);
|
2014-08-06 23:04:59 +00:00
|
|
|
void * __meminit alloc_pages_exact_nid(int nid, size_t size, gfp_t gfp_mask);
|
2008-07-24 04:28:11 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#define __get_free_page(gfp_mask) \
|
2010-05-24 21:32:45 +00:00
|
|
|
__get_free_pages((gfp_mask), 0)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
#define __get_dma_pages(gfp_mask, order) \
|
2010-05-24 21:32:45 +00:00
|
|
|
__get_free_pages((gfp_mask) | GFP_DMA, (order))
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-02-13 23:03:15 +00:00
|
|
|
extern void __free_pages(struct page *page, unsigned int order);
|
|
|
|
extern void free_pages(unsigned long addr, unsigned int order);
|
2014-06-04 23:10:22 +00:00
|
|
|
extern void free_hot_cold_page(struct page *page, bool cold);
|
|
|
|
extern void free_hot_cold_page_list(struct list_head *list, bool cold);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2015-05-07 04:11:57 +00:00
|
|
|
struct page_frag_cache;
|
|
|
|
extern void *__alloc_page_frag(struct page_frag_cache *nc,
|
|
|
|
unsigned int fragsz, gfp_t gfp_mask);
|
|
|
|
extern void __free_page_frag(void *addr);
|
|
|
|
|
2014-06-04 23:06:39 +00:00
|
|
|
extern void __free_kmem_pages(struct page *page, unsigned int order);
|
|
|
|
extern void free_kmem_pages(unsigned long addr, unsigned int order);
|
2012-12-18 22:22:00 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#define __free_page(page) __free_pages((page), 0)
|
2010-05-24 21:32:45 +00:00
|
|
|
#define free_page(addr) free_pages((addr), 0)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
void page_alloc_init(void);
|
2007-05-09 09:35:14 +00:00
|
|
|
void drain_zone_pages(struct zone *zone, struct per_cpu_pages *pcp);
|
2014-12-10 23:43:01 +00:00
|
|
|
void drain_all_pages(struct zone *zone);
|
|
|
|
void drain_local_pages(struct zone *zone);
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2015-06-30 21:57:27 +00:00
|
|
|
#ifdef CONFIG_DEFERRED_STRUCT_PAGE_INIT
|
|
|
|
void page_alloc_init_late(void);
|
|
|
|
#else
|
|
|
|
static inline void page_alloc_init_late(void)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
2012-01-10 23:07:15 +00:00
|
|
|
/*
|
|
|
|
* gfp_allowed_mask is set to GFP_BOOT_MASK during early boot to restrict what
|
|
|
|
* GFP flags are used before interrupts are enabled. Once interrupts are
|
|
|
|
* enabled, it is set to __GFP_BITS_MASK while the system is running. During
|
|
|
|
* hibernation, it is used by PM to avoid I/O during memory allocation while
|
|
|
|
* devices are suspended.
|
|
|
|
*/
|
2009-06-18 03:24:12 +00:00
|
|
|
extern gfp_t gfp_allowed_mask;
|
|
|
|
|
2012-07-31 23:44:19 +00:00
|
|
|
/* Returns true if the gfp_mask allows use of ALLOC_NO_WATERMARK */
|
|
|
|
bool gfp_pfmemalloc_allowed(gfp_t gfp_mask);
|
|
|
|
|
2010-12-03 21:57:45 +00:00
|
|
|
extern void pm_restrict_gfp_mask(void);
|
|
|
|
extern void pm_restore_gfp_mask(void);
|
2009-06-18 03:24:12 +00:00
|
|
|
|
2012-01-10 23:07:15 +00:00
|
|
|
#ifdef CONFIG_PM_SLEEP
|
|
|
|
extern bool pm_suspended_storage(void);
|
|
|
|
#else
|
|
|
|
static inline bool pm_suspended_storage(void)
|
|
|
|
{
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
#endif /* CONFIG_PM_SLEEP */
|
|
|
|
|
2016-02-05 23:36:41 +00:00
|
|
|
#if (defined(CONFIG_MEMORY_ISOLATION) && defined(CONFIG_COMPACTION)) || defined(CONFIG_CMA)
|
2011-12-29 12:09:50 +00:00
|
|
|
/* The below functions must be run on a range from a single zone. */
|
2012-04-03 13:06:15 +00:00
|
|
|
extern int alloc_contig_range(unsigned long start, unsigned long end,
|
|
|
|
unsigned migratetype);
|
2011-12-29 12:09:50 +00:00
|
|
|
extern void free_contig_range(unsigned long pfn, unsigned nr_pages);
|
2016-02-05 23:36:41 +00:00
|
|
|
#endif
|
2011-12-29 12:09:50 +00:00
|
|
|
|
2016-02-05 23:36:41 +00:00
|
|
|
#ifdef CONFIG_CMA
|
2011-12-29 12:09:50 +00:00
|
|
|
/* CMA stuff */
|
|
|
|
extern void init_cma_reserved_pageblock(struct page *page);
|
2011-12-29 12:09:50 +00:00
|
|
|
#endif
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#endif /* __LINUX_GFP_H */
|