From: Muchun Song <songmuchun@bytedance.com>
To: mike.kravetz@oracle.com, akpm@linux-foundation.org, david@redhat.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
smuchun@bytedance.com, Muchun Song <songmuchun@bytedance.com>
Subject: [PATCH 0/3] cleanup hugetlb_vmemmap
Date: Mon, 4 Apr 2022 15:46:49 +0800 [thread overview]
Message-ID: <20220404074652.68024-1-songmuchun@bytedance.com> (raw)
This series is based on next-20220404.
The word of "free" is not expressive enough to express the feature of optimizing
vmemmap pages associated with each HugeTLB, rename this keywork to "optimeze" is
more clear. In this series, cheanup related codes to make it more clear and
expressive. This is suggested by David.
Muchun Song (3):
mm: hugetlb_vmemmap: cleanup hugetlb_vmemmap related functions
mm: hugetlb_vmemmap: cleanup hugetlb_free_vmemmap_enabled*
mm: hugetlb_vmemmap: cleanup CONFIG_HUGETLB_PAGE_FREE_VMEMMAP*
Documentation/admin-guide/kernel-parameters.txt | 4 +-
Documentation/admin-guide/mm/hugetlbpage.rst | 2 +-
arch/arm64/Kconfig | 2 +-
arch/arm64/mm/flush.c | 4 +-
arch/x86/Kconfig | 2 +-
arch/x86/mm/init_64.c | 2 +-
fs/Kconfig | 16 +++----
include/linux/hugetlb.h | 4 +-
include/linux/mm.h | 2 +-
include/linux/page-flags.h | 18 ++++----
mm/Makefile | 2 +-
mm/hugetlb.c | 10 ++---
mm/hugetlb_vmemmap.c | 56 ++++++++++++-------------
mm/hugetlb_vmemmap.h | 24 +++++------
mm/memory_hotplug.c | 2 +-
mm/sparse-vmemmap.c | 4 +-
16 files changed, 76 insertions(+), 78 deletions(-)
--
2.11.0
next reply other threads:[~2022-04-04 7:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 7:46 Muchun Song [this message]
2022-04-04 7:46 ` [PATCH 1/3] mm: hugetlb_vmemmap: cleanup hugetlb_vmemmap related functions Muchun Song
2022-05-31 23:47 ` Mike Kravetz
2022-05-31 23:58 ` Mike Kravetz
2022-06-01 9:28 ` David Hildenbrand
2022-06-01 10:48 ` Muchun Song
2022-06-01 10:49 ` David Hildenbrand
2022-04-04 7:46 ` [PATCH 2/3] mm: hugetlb_vmemmap: cleanup hugetlb_free_vmemmap_enabled* Muchun Song
2022-06-01 0:01 ` Mike Kravetz
2022-06-01 9:29 ` David Hildenbrand
2022-04-04 7:46 ` [PATCH 3/3] mm: hugetlb_vmemmap: cleanup CONFIG_HUGETLB_PAGE_FREE_VMEMMAP* Muchun Song
2022-05-27 7:39 ` Vlastimil Babka
2022-05-27 7:47 ` Muchun Song
2022-06-01 0:20 ` Mike Kravetz
2022-06-01 9:32 ` David Hildenbrand
2022-06-01 9:54 ` Muchun Song
2022-06-01 10:10 ` David Hildenbrand
2022-06-01 11:56 ` 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=20220404074652.68024-1-songmuchun@bytedance.com \
--to=songmuchun@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=smuchun@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