From: Muchun Song <songmuchun@bytedance.com>
To: akpm@linux-foundation.org, corbet@lwn.net, david@redhat.com,
mike.kravetz@oracle.com, osalvador@suse.de, paulmck@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, duanxiongchun@bytedance.com,
smuchun@gmail.com, Muchun Song <songmuchun@bytedance.com>
Subject: [PATCH v3 0/2] make hugetlb_optimize_vmemmap compatible with memmap_on_memory
Date: Fri, 17 Jun 2022 21:56:48 +0800 [thread overview]
Message-ID: <20220617135650.74901-1-songmuchun@bytedance.com> (raw)
This series makes hugetlb_optimize_vmemmap compatible with memmap_on_memory
and is based on mm-stable. The reason refers to the patch 2's commit log.
v3:
- Switch complicated enumeration magic (David).
- Introduce PageVmemmapSelfHosted to make both parameters compatible (David and Oscar).
v2:
- Fix compile error when !CONFIG_ZONE_DEVICE reported by kernel test robot.
Muchun Song (2):
mm: memory_hotplug: enumerate all supported section flags
mm: memory_hotplug: make hugetlb_optimize_vmemmap compatible with
memmap_on_memory
Documentation/admin-guide/kernel-parameters.txt | 22 ++++++------
Documentation/admin-guide/sysctl/vm.rst | 5 ++-
include/linux/memory_hotplug.h | 9 -----
include/linux/mmzone.h | 44 ++++++++++++++++++-----
include/linux/page-flags.h | 11 ++++++
mm/hugetlb_vmemmap.c | 47 ++++++++++++++++++++-----
mm/memory_hotplug.c | 33 ++++++++---------
mm/sparse.c | 2 +-
8 files changed, 116 insertions(+), 57 deletions(-)
base-commit: 6edda04ccc7cfb281d139e352dbd5dd933bd2751
--
2.11.0
next reply other threads:[~2022-06-17 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 13:56 Muchun Song [this message]
2022-06-17 13:56 ` [PATCH v3 1/2] mm: memory_hotplug: enumerate all supported section flags Muchun Song
2022-06-17 13:56 ` [PATCH v3 2/2] mm: memory_hotplug: make hugetlb_optimize_vmemmap compatible with memmap_on_memory 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=20220617135650.74901-1-songmuchun@bytedance.com \
--to=songmuchun@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=duanxiongchun@bytedance.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
--cc=paulmck@kernel.org \
--cc=smuchun@gmail.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