[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75318c8e-11fb-7d2a-1296-db1b06351aea@arm.com>
Date: Tue, 13 Sep 2022 14:38:31 +0530
From: Anshuman Khandual <anshuman.khandual@....com>
To: Miaohe Lin <linmiaohe@...wei.com>, akpm@...ux-foundation.org
Cc: david@...hat.com, osalvador@...e.de, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 14/16] mm/page_alloc: use costly_order in
WARN_ON_ONCE_GFP()
On 9/9/22 14:54, Miaohe Lin wrote:
> There's no need to check whether order > PAGE_ALLOC_COSTLY_ORDER again.
> Minor readability improvement.
>
> Signed-off-by: Miaohe Lin <linmiaohe@...wei.com>
Reviewed-by: Anshuman Khandual <anshuman.khandual@....com>
> ---
> mm/page_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 63ad25e86010..262e8972e019 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5272,7 +5272,7 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
> * 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
Powered by blists - more mailing lists