From: Muchun Song <songmuchun@bytedance.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
Joao Martins <joao.m.martins@oracle.com>,
Dan Williams <dan.j.williams@intel.com>,
muchun.song@linux.dev
Subject: Re: [External] [PATCH v2 2/2] m/hugetlb: Rename ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP
Date: Wed, 12 Apr 2023 11:43:49 +0800 [thread overview]
Message-ID: <CAMZfGtVBVwF-Uep9YQAA=kp9p2bs3B9XQWP832ayia98qswUNg@mail.gmail.com> (raw)
In-Reply-To: <20230411141818.62152-2-aneesh.kumar@linux.ibm.com>
On Tue, Apr 11, 2023 at 10:18 PM Aneesh Kumar K.V
<aneesh.kumar@linux.ibm.com> wrote:
>
> Now we use ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP config option
> to indicate devdax and hugetlb vmemmap optimization support. Hence
> rename that to a generic ARCH_WANT_OPTIMIZE_VMEMMAP
>
> Cc: Joao Martins <joao.m.martins@oracle.com>
> Cc: Muchun Song <songmuchun@bytedance.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
I suggest rewording the prefix of subject to "mm/hugetlb_vmemmap:".
Renaming LGTM.
Reviewed-by: Muchun Song <songmuchun@bytedance.com>
Thanks.
next prev parent reply other threads:[~2023-04-12 3:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 14:18 [PATCH v2 1/2] mm/vmemmap/devdax: Fix kernel crash when probing devdax devices Aneesh Kumar K.V
2023-04-11 14:18 ` [PATCH v2 2/2] m/hugetlb: Rename ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP Aneesh Kumar K.V
2023-04-11 15:52 ` Joao Martins
2023-04-11 16:14 ` Aneesh Kumar K V
2023-04-11 17:34 ` Joao Martins
2023-04-12 3:43 ` Muchun Song [this message]
2023-04-11 14:35 ` [PATCH v2 1/2] mm/vmemmap/devdax: Fix kernel crash when probing devdax devices Joao Martins
2023-04-11 15:20 ` Aneesh Kumar K.V
2023-04-11 15:50 ` Joao Martins
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='CAMZfGtVBVwF-Uep9YQAA=kp9p2bs3B9XQWP832ayia98qswUNg@mail.gmail.com' \
--to=songmuchun@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=joao.m.martins@oracle.com \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
/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