[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f25c03d7-d9e2-2ae3-4dcc-0d054a15ad2c@suse.cz>
Date: Fri, 27 May 2022 09:39:41 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Muchun Song <songmuchun@...edance.com>, mike.kravetz@...cle.com,
akpm@...ux-foundation.org, david@...hat.com
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
smuchun@...edance.com
Subject: Re: [PATCH 3/3] mm: hugetlb_vmemmap: cleanup
CONFIG_HUGETLB_PAGE_FREE_VMEMMAP*
On 4/4/22 09:46, Muchun Song wrote:
> --- a/mm/hugetlb_vmemmap.c
> +++ b/mm/hugetlb_vmemmap.c
> @@ -188,7 +188,7 @@
> #define RESERVE_VMEMMAP_NR 1U
> #define RESERVE_VMEMMAP_SIZE (RESERVE_VMEMMAP_NR << PAGE_SHIFT)
>
> -DEFINE_STATIC_KEY_MAYBE(CONFIG_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON,
> +DEFINE_STATIC_KEY_MAYBE(CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_ON,
> hugetlb_optimize_vmemmap_key);
> EXPORT_SYMBOL(hugetlb_optimize_vmemmap_key);
Hi,
looks like just below here you forgot to update:
static enum vmemmap_optimize_mode vmemmap_optimize_mode =
IS_ENABLED(CONFIG_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON);
so it refers to CONFIG name that no longer exists?
Vlastimil
Powered by blists - more mailing lists