From: Muchun Song <songmuchun@bytedance.com>
To: corbet@lwn.net, akpm@linux-foundation.org, paulmck@kernel.org,
mike.kravetz@oracle.com, osalvador@suse.de, david@redhat.com
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 v2 0/2] make hugetlb_optimize_vmemmap compatible with memmap_on_memory
Date: Fri, 20 May 2022 10:55:36 +0800 [thread overview]
Message-ID: <20220520025538.21144-1-songmuchun@bytedance.com> (raw)
This series makes hugetlb_optimize_vmemmap compatible with memmap_on_memory
and is based on next-20220518. The reason refers to the patch 2's commit log.
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: introduce SECTION_CANNOT_OPTIMIZE_VMEMMAP
Documentation/admin-guide/kernel-parameters.txt | 22 ++++----
Documentation/admin-guide/sysctl/vm.rst | 5 +-
include/linux/kconfig.h | 1 +
include/linux/memory_hotplug.h | 9 ----
include/linux/mmzone.h | 71 ++++++++++++++++++++++---
mm/hugetlb_vmemmap.c | 28 +++++++---
mm/memory_hotplug.c | 28 +++++-----
mm/sparse.c | 8 +++
8 files changed, 119 insertions(+), 53 deletions(-)
--
2.11.0
next reply other threads:[~2022-05-20 2:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 2:55 Muchun Song [this message]
2022-05-20 2:55 ` [PATCH v2 1/2] mm: memory_hotplug: enumerate all supported section flags Muchun Song
2022-06-15 9:35 ` David Hildenbrand
2022-06-15 13:02 ` Muchun Song
2022-05-20 2:55 ` [PATCH v2 2/2] mm: memory_hotplug: introduce SECTION_CANNOT_OPTIMIZE_VMEMMAP Muchun Song
2022-06-15 9:51 ` David Hildenbrand
2022-06-16 2:45 ` Muchun Song
2022-06-16 7:21 ` David Hildenbrand
2022-06-16 10:16 ` Muchun Song
2022-06-16 3:57 ` Oscar Salvador
2022-06-16 7:30 ` David Hildenbrand
2022-06-17 5:46 ` Oscar Salvador
2022-06-17 7:28 ` Muchun Song
2022-06-17 7:39 ` David Hildenbrand
2022-06-17 9:10 ` Muchun Song
2022-06-17 9:25 ` David Hildenbrand
2022-06-17 9:40 ` Muchun Song
2022-06-17 9:48 ` Oscar Salvador
2022-06-17 7:43 ` David Hildenbrand
2022-06-17 9:54 ` Oscar Salvador
2022-06-17 10:14 ` David Hildenbrand
2022-06-17 10:49 ` Muchun Song
2022-06-17 11:19 ` Muchun Song
2022-06-18 5:49 ` 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=20220520025538.21144-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;
as well as URLs for NNTP newsgroup(s).