From: Joao Martins <joao.m.martins@oracle.com>
To: Muchun Song <songmuchun@bytedance.com>, mike.kravetz@oracle.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, akpm@linux-foundation.org,
corbet@lwn.net, david@redhat.com
Subject: Re: [PATCH 3/6] mm: hugetlb_vmemmap: introduce the name HVO
Date: Wed, 15 Jun 2022 15:51:51 +0100 [thread overview]
Message-ID: <41e2d762-2c0d-b13b-d6da-6e0e0e858a84@oracle.com> (raw)
In-Reply-To: <20220613063512.17540-4-songmuchun@bytedance.com>
On 6/13/22 07:35, Muchun Song wrote:
> It it inconvenient to mention the feature of optimizing vmemmap pages associated
> with HugeTLB pages when communicating with others since there is no specific or
> abbreviated name for it when it is first introduced. Let us give it a name HVO
> (HugeTLB Vmemmap Optimization) from now.
>
Just thought I would throw this suggestion, even though I am probably too late.
I find the term "vmemmap deduplication" more self-explanatory (at least for me)
to refer to your technique ,and similarly s/optimize/dedup. Or vmemmap tail page
deduplication (too verbose maybe) because really that's what this optimization is all
about. OTOH it would slightly deviate from what maybe established now
in hugetlb code.
next prev parent reply other threads:[~2022-06-15 14:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 6:35 [PATCH 0/6] Simplify hugetlb vmemmap and improve its readability Muchun Song
2022-06-13 6:35 ` [PATCH 1/6] mm: hugetlb_vmemmap: delete hugetlb_optimize_vmemmap_enabled() Muchun Song
2022-06-13 8:04 ` Oscar Salvador
2022-06-13 18:15 ` Mike kravetz
2022-06-20 16:57 ` Catalin Marinas
2022-06-13 6:35 ` [PATCH 2/6] mm: hugetlb_vmemmap: optimize vmemmap_optimize_mode handling Muchun Song
2022-06-13 8:10 ` Oscar Salvador
2022-06-13 8:24 ` Muchun Song
2022-06-13 18:28 ` Mike kravetz
2022-06-13 6:35 ` [PATCH 3/6] mm: hugetlb_vmemmap: introduce the name HVO Muchun Song
2022-06-13 8:13 ` Oscar Salvador
2022-06-13 15:39 ` David Hildenbrand
2022-06-14 3:15 ` Muchun Song
2022-06-13 21:19 ` Mike Kravetz
2022-06-14 3:17 ` Muchun Song
2022-06-15 14:51 ` Joao Martins [this message]
2022-06-16 3:28 ` Muchun Song
2022-06-16 22:27 ` Mike Kravetz
2022-06-17 7:49 ` Muchun Song
2022-06-13 6:35 ` [PATCH 4/6] mm: hugetlb_vmemmap: move vmemmap code related to HugeTLB to hugetlb_vmemmap.c Muchun Song
2022-06-13 8:15 ` Oscar Salvador
2022-06-13 21:34 ` Mike Kravetz
2022-06-13 6:35 ` [PATCH 5/6] mm: hugetlb_vmemmap: replace early_param() with core_param() Muchun Song
2022-06-13 21:43 ` Mike Kravetz
2022-06-13 6:35 ` [PATCH 6/6] mm: hugetlb_vmemmap: improve hugetlb_vmemmap code readability Muchun Song
2022-06-13 8:33 ` Oscar Salvador
2022-06-13 9:01 ` Muchun Song
2022-06-14 0:22 ` Mike Kravetz
2022-06-14 4:17 ` Muchun Song
2022-06-14 16:57 ` Mike Kravetz
2022-06-15 12:33 ` 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=41e2d762-2c0d-b13b-d6da-6e0e0e858a84@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=songmuchun@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: 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;
as well as URLs for NNTP newsgroup(s).