Commit 916a9f38 authored by Arnaldo Carvalho de Melo's avatar Arnaldo Carvalho de Melo
Browse files

tools headers: Update the linux/gfp_types.h copy with the kernel sources 



To pick up the changes in:

  f3ec502b ("mm/slab: mark alloc tags empty for sheaves allocated with __GFP_NO_OBJ_EXT")
  241b3a09 ("mm: clarify GFP_ATOMIC/GFP_NOWAIT doc-comment")

That just adds some comments, so no changes in perf tooling, just silences
this build warning:

Warning: Kernel ABI header differences:
  diff -u tools/include/linux/gfp_types.h include/linux/gfp_types.h

Please see tools/include/uapi/README.

Signed-off-by: default avatarArnaldo Carvalho de Melo <acme@redhat.com>
parent ecd5a2fd

tools/include/linux/gfp_types.h

+7 −2
Original line number Diff line number Diff line
@@ -139,6 +139,8 @@ enum { 
 * %__GFP_ACCOUNT causes the allocation to be accounted to kmemcg.

 *

 * %__GFP_NO_OBJ_EXT causes slab allocation to have no object extension.

 * mark_obj_codetag_empty() should be called upon freeing for objects allocated

 * with this flag to indicate that their NULL tags are expected and normal.

 */

#define __GFP_RECLAIMABLE ((__force gfp_t)___GFP_RECLAIMABLE)

#define __GFP_WRITE	((__force gfp_t)___GFP_WRITE)
@@ -309,8 +311,10 @@ enum { 
 *

 * %GFP_ATOMIC users can not sleep and need the allocation to succeed. A lower

 * watermark is applied to allow access to "atomic reserves".

 * The current implementation doesn't support NMI and few other strict

 * non-preemptive contexts (e.g. raw_spin_lock). The same applies to %GFP_NOWAIT.

 * The current implementation doesn't support NMI, nor contexts that disable

 * preemption under PREEMPT_RT. This includes raw_spin_lock() and plain

 * preempt_disable() - see "Memory allocation" in

 * Documentation/core-api/real-time/differences.rst for more info.

 *

 * %GFP_KERNEL is typical for kernel-internal allocations. The caller requires

 * %ZONE_NORMAL or a lower zone for direct access but can direct reclaim.
@@ -321,6 +325,7 @@ enum { 
 * %GFP_NOWAIT is for kernel allocations that should not stall for direct

 * reclaim, start physical IO or use any filesystem callback.  It is very

 * likely to fail to allocate memory, even for very small allocations.

 * The same restrictions on calling contexts apply as for %GFP_ATOMIC.

 *

 * %GFP_NOIO will use direct reclaim to discard clean pages or slab pages

 * that do not require the starting of any physical IO.