The patch titled
Subject: mm-clarify-__gfp_memalloc-usage-update
has been removed from the -mm tree. Its filename was
mm-clarify-__gfp_memalloc-usage-update.patch
This patch was dropped because it was folded into mm-clarify-__gfp_memalloc-usage.patch
------------------------------------------------------
From: Michal Hocko <mhocko@xxxxxxxxxx>
Subject: mm-clarify-__gfp_memalloc-usage-update
Link: http://lkml.kernel.org/r/20200406070137.GC19426@xxxxxxxxxxxxxx
Signed-off-by: Michal Hocko <mhocko@xxxxxxxx>
Cc: David Rientjes <rientjes@xxxxxxxxxx>
Cc: Joel Fernandes <joel@xxxxxxxxxxxxxxxxx>
Cc: John Hubbard <jhubbard@xxxxxxxxxx>
Cc: Neil Brown <neilb@xxxxxxx>
Cc: Paul E. McKenney <paulmck@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/gfp.h | 2 ++
1 file changed, 2 insertions(+)
--- a/include/linux/gfp.h~mm-clarify-__gfp_memalloc-usage-update
+++ a/include/linux/gfp.h
@@ -113,6 +113,8 @@ struct vm_area_struct;
* Users of this flag have to be extremely careful to not deplete the reserve
* completely and implement a throttling mechanism which controls the consumption
* of the reserve based on the amount of freed memory.
+ * Usage of a pre-allocated pool (e.g. mempool) should be always considered before
+ * using this flag.
*
* %__GFP_NOMEMALLOC is used to explicitly forbid access to emergency reserves.
* This takes precedence over the %__GFP_MEMALLOC flag if both are set.
_
Patches currently in -mm which might be from mhocko@xxxxxxxxxx are
mm-clarify-__gfp_memalloc-usage.patch
