mm/page_alloc: use costly_order in WARN_ON_ONCE_GFP()
authorMiaohe Lin <linmiaohe@huawei.com>
Fri, 16 Sep 2022 07:22:55 +0000 (15:22 +0800)
committerAndrew Morton <akpm@linux-foundation.org>
Mon, 3 Oct 2022 21:03:30 +0000 (14:03 -0700)
There's no need to check whether order > PAGE_ALLOC_COSTLY_ORDER again.
Minor readability improvement.

Link: https://lkml.kernel.org/r/20220916072257.9639-15-linmiaohe@huawei.com
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
Cc: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
mm/page_alloc.c

index 4dc2fe575fc8dfb8e3996ac066a8448bc18dacc0..23f839e1d89e3db6df5a23cc008eead4ff933751 100644 (file)
@@ -5280,7 +5280,7 @@ nopage:
                 * so that we can identify them and convert them to something
                 * else.
                 */
-               WARN_ON_ONCE_GFP(order > PAGE_ALLOC_COSTLY_ORDER, gfp_mask);
+               WARN_ON_ONCE_GFP(costly_order, gfp_mask);
 
                /*
                 * Help non-failing allocations by giving them access to memory