From: Muchun Song <songmuchun@bytedance.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
David Hildenbrand <david@redhat.com>,
"Bodeddula, Balasubramaniam" <bodeddub@amazon.com>,
Oscar Salvador <osalvador@suse.de>,
Mike Kravetz <mike.kravetz@oracle.com>,
David Rientjes <rientjes@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
james.morse@arm.com, Barry Song <21cnbao@gmail.com>,
LAK <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Xiongchun duan <duanxiongchun@bytedance.com>,
Fam Zheng <fam.zheng@bytedance.com>,
Muchun Song <smuchun@gmail.com>
Subject: Re: [PATCH v3] arm64: mm: hugetlb: Enable HUGETLB_PAGE_FREE_VMEMMAP for arm64
Date: Thu, 31 Mar 2022 10:46:25 +0800 [thread overview]
Message-ID: <CAMZfGtWqsQsyr6-R1CtA9Uzswrb7MRXbBZqa4VKA9NCYyVvKOA@mail.gmail.com> (raw)
In-Reply-To: <20220330194147.000c80ef35345397756e096e@linux-foundation.org>
On Thu, Mar 31, 2022 at 10:41 AM Andrew Morton
<akpm@linux-foundation.org> wrote:
>
> On Wed, 30 Mar 2022 22:54:00 +0800 Muchun Song <songmuchun@bytedance.com> wrote:
>
> > --- a/fs/Kconfig
> > +++ b/fs/Kconfig
> > @@ -247,7 +247,7 @@ config HUGETLB_PAGE
> >
> > config HUGETLB_PAGE_FREE_VMEMMAP
> > def_bool HUGETLB_PAGE
> > - depends on X86_64
> > + depends on X86_64 || ARM64
>
> This list is just going to get longer, until someone goes and switches
> it to use ARCH_WANT_HUGETLB_PAGE_FREE_VMEMMAP or whatever. Why not do
> that now?
Good suggestion. Yep, the line is going to be long if someone
wants to enable it for other architectures in the future. Will do.
Thanks.
prev parent reply other threads:[~2022-03-31 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 14:54 Muchun Song
2022-03-31 2:41 ` Andrew Morton
2022-03-31 2:46 ` Muchun Song [this message]
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=CAMZfGtWqsQsyr6-R1CtA9Uzswrb7MRXbBZqa4VKA9NCYyVvKOA@mail.gmail.com \
--to=songmuchun@bytedance.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bodeddub@amazon.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=duanxiongchun@bytedance.com \
--cc=fam.zheng@bytedance.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=smuchun@gmail.com \
--cc=will@kernel.org \
/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: link
Be 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