LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com> To: Muchun Song <songmuchun@bytedance.com> Cc: mike.kravetz@oracle.com, Andrew Morton <akpm@linux-foundation.org>, osalvador@suse.de, mhocko@suse.com, Barry Song <song.bao.hua@hisilicon.com>, david@redhat.com, chenhuang5@huawei.com, bodeddub@amazon.com, Jonathan Corbet <corbet@lwn.net>, Matthew Wilcox <willy@infradead.org>, duanxiongchun@bytedance.com, fam.zheng@bytedance.com, smuchun@gmail.com, zhengqi.arch@bytedance.com, linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>, Linux-MM <linux-mm@kvack.org> Subject: Re: [PATCH RESEND v2 2/4] mm: hugetlb: replace hugetlb_free_vmemmap_enabled with a static_key Date: Sat, 18 Sep 2021 16:55:36 +1200 [thread overview] Message-ID: <CAGsJ_4ymutSL-pbWA_TykJ2vE8ZKc+JGn+w_WWy2j7Mn-q+ebA@mail.gmail.com> (raw) In-Reply-To: <20210917034815.80264-3-songmuchun@bytedance.com> On Sat, Sep 18, 2021 at 12:08 AM Muchun Song <songmuchun@bytedance.com> wrote: > > The page_head_if_fake() is used throughout memory management and the > conditional check requires checking a global variable, although the > overhead of this check may be small, it increases when the memory > cache comes under pressure. Also, the global variable will not be > modified after system boot, so it is very appropriate to use static > key machanism. > > Signed-off-by: Muchun Song <songmuchun@bytedance.com> > --- > include/linux/hugetlb.h | 6 +++++- > include/linux/page-flags.h | 6 ++++-- > mm/hugetlb_vmemmap.c | 10 +++++----- > 3 files changed, 14 insertions(+), 8 deletions(-) > > diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h > index f7ca1a3870ea..ee3ddf3d12cf 100644 > --- a/include/linux/hugetlb.h > +++ b/include/linux/hugetlb.h > @@ -1057,7 +1057,11 @@ static inline void set_huge_swap_pte_at(struct mm_struct *mm, unsigned long addr > #endif /* CONFIG_HUGETLB_PAGE */ > > #ifdef CONFIG_HUGETLB_PAGE_FREE_VMEMMAP > -extern bool hugetlb_free_vmemmap_enabled; > +DECLARE_STATIC_KEY_MAYBE(CONFIG_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON, > + hugetlb_free_vmemmap_enabled_key); > +#define hugetlb_free_vmemmap_enabled \ > + static_key_enabled(&hugetlb_free_vmemmap_enabled_key) > + > #else > #define hugetlb_free_vmemmap_enabled false > #endif > diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h > index 7b1a918ebd43..d68d2cf30d76 100644 > --- a/include/linux/page-flags.h > +++ b/include/linux/page-flags.h > @@ -185,7 +185,8 @@ enum pageflags { > #ifndef __GENERATING_BOUNDS_H > > #ifdef CONFIG_HUGETLB_PAGE_FREE_VMEMMAP > -extern bool hugetlb_free_vmemmap_enabled; > +DECLARE_STATIC_KEY_MAYBE(CONFIG_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON, > + hugetlb_free_vmemmap_enabled_key); > > /* > * If the feature of freeing some vmemmap pages associated with each HugeTLB > @@ -204,7 +205,8 @@ extern bool hugetlb_free_vmemmap_enabled; > */ > static __always_inline const struct page *page_head_if_fake(const struct page *page) > { > - if (!hugetlb_free_vmemmap_enabled) > + if (!static_branch_maybe(CONFIG_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON, > + &hugetlb_free_vmemmap_enabled_key)) A question bothering me is that we still have hugetlb_free_vmemmap_enabled defined as static_key_enabled(&hugetlb_free_vmemmap_enabled_key). but here you are using static_branch_maybe() with the CONFIG and refer the key directly. Do we only need one of them? Or something is wrong? > return page; > > /* > diff --git a/mm/hugetlb_vmemmap.c b/mm/hugetlb_vmemmap.c > index 527bcaa44a48..5b80129c684c 100644 > --- a/mm/hugetlb_vmemmap.c > +++ b/mm/hugetlb_vmemmap.c > @@ -188,9 +188,9 @@ > #define RESERVE_VMEMMAP_NR 1U > #define RESERVE_VMEMMAP_SIZE (RESERVE_VMEMMAP_NR << PAGE_SHIFT) > > -bool hugetlb_free_vmemmap_enabled __read_mostly = > - IS_ENABLED(CONFIG_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON); > -EXPORT_SYMBOL(hugetlb_free_vmemmap_enabled); > +DEFINE_STATIC_KEY_MAYBE(CONFIG_HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON, > + hugetlb_free_vmemmap_enabled_key); > +EXPORT_SYMBOL(hugetlb_free_vmemmap_enabled_key); > > static int __init early_hugetlb_free_vmemmap_param(char *buf) > { > @@ -204,9 +204,9 @@ static int __init early_hugetlb_free_vmemmap_param(char *buf) > return -EINVAL; > > if (!strcmp(buf, "on")) > - hugetlb_free_vmemmap_enabled = true; > + static_branch_enable(&hugetlb_free_vmemmap_enabled_key); > else if (!strcmp(buf, "off")) > - hugetlb_free_vmemmap_enabled = false; > + static_branch_disable(&hugetlb_free_vmemmap_enabled_key); > else > return -EINVAL; > > -- > 2.11.0 > Thanks barry
next prev parent reply other threads:[~2021-09-18 4:55 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-17 3:48 [PATCH RESEND v2 0/4] Free the 2nd vmemmap page associated with each HugeTLB page Muchun Song 2021-09-17 3:48 ` [PATCH RESEND v2 1/4] mm: hugetlb: free " Muchun Song 2021-09-18 4:38 ` Barry Song 2021-09-18 10:06 ` Muchun Song 2021-09-21 6:43 ` Muchun Song 2021-09-21 10:22 ` Muchun Song 2021-09-21 0:11 ` Barry Song 2021-09-21 13:46 ` Muchun Song 2021-09-21 20:43 ` Barry Song 2021-09-22 2:38 ` Muchun Song 2021-09-22 7:36 ` Barry Song 2021-09-17 3:48 ` [PATCH RESEND v2 2/4] mm: hugetlb: replace hugetlb_free_vmemmap_enabled with a static_key Muchun Song 2021-09-18 4:55 ` Barry Song [this message] 2021-09-18 10:30 ` Muchun Song 2021-09-18 11:14 ` Barry Song 2021-09-18 11:47 ` Muchun Song 2021-09-18 12:27 ` Barry Song 2021-09-17 3:48 ` [PATCH RESEND v2 3/4] mm: sparsemem: use page table lock to protect kernel pmd operations Muchun Song 2021-09-18 5:06 ` Barry Song 2021-09-18 10:51 ` Muchun Song 2021-09-18 11:01 ` Barry Song 2021-09-17 3:48 ` [PATCH RESEND v2 4/4] selftests: vm: add a hugetlb test case Muchun Song 2021-09-18 5:20 ` Barry Song 2021-09-20 14:26 ` Muchun Song 2021-09-21 0:28 ` Barry Song 2021-09-21 13:18 ` Muchun Song
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAGsJ_4ymutSL-pbWA_TykJ2vE8ZKc+JGn+w_WWy2j7Mn-q+ebA@mail.gmail.com \ --to=21cnbao@gmail.com \ --cc=akpm@linux-foundation.org \ --cc=bodeddub@amazon.com \ --cc=chenhuang5@huawei.com \ --cc=corbet@lwn.net \ --cc=david@redhat.com \ --cc=duanxiongchun@bytedance.com \ --cc=fam.zheng@bytedance.com \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@suse.com \ --cc=mike.kravetz@oracle.com \ --cc=osalvador@suse.de \ --cc=smuchun@gmail.com \ --cc=song.bao.hua@hisilicon.com \ --cc=songmuchun@bytedance.com \ --cc=willy@infradead.org \ --cc=zhengqi.arch@bytedance.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).