From: Muchun Song <songmuchun@bytedance.com>
To: corbet@lwn.net, mike.kravetz@oracle.com,
akpm@linux-foundation.org, mcgrof@kernel.org,
keescook@chromium.org, yzaikin@google.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/3] add hugetlb_free_vmemmap sysctl
Date: Wed, 2 Mar 2022 16:37:55 +0800 [thread overview]
Message-ID: <20220302083758.32528-1-songmuchun@bytedance.com> (raw)
This series amis to add hugetlb_free_vmemmap sysctl to enable the feature
of freeing vmemmap pages of HugeTLB pages.
v2:
- Fix compilation when !CONFIG_MHP_MEMMAP_ON_MEMORY reported by kernel
test robot <lkp@intel.com>.
- Move sysctl code from kernel/sysctl.c to mm/hugetlb_vmemmap.c.
Muchun Song (3):
mm: hugetlb: disable freeing vmemmap pages when struct page crosses
page boundaries
sysctl: allow to set extra1 to SYSCTL_ONE
mm: hugetlb: add hugetlb_free_vmemmap sysctl
Documentation/admin-guide/sysctl/vm.rst | 13 ++++++++++
include/linux/memory_hotplug.h | 9 +++++++
kernel/sysctl.c | 2 +-
mm/hugetlb_vmemmap.c | 43 ++++++++++++++++++++++++++++++++-
mm/hugetlb_vmemmap.h | 4 ++-
mm/memory_hotplug.c | 5 ++++
6 files changed, 73 insertions(+), 3 deletions(-)
--
2.11.0
next reply other threads:[~2022-03-02 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 8:37 Muchun Song [this message]
2022-03-02 8:37 ` [PATCH v2 1/3] mm: hugetlb: disable freeing vmemmap pages when struct page crosses page boundaries Muchun Song
2022-03-02 21:21 ` Luis Chamberlain
2022-03-03 2:38 ` Muchun Song
2022-03-03 0:25 ` Mike Kravetz
2022-03-03 2:28 ` Muchun Song
2022-03-02 8:37 ` [PATCH v2 2/3] sysctl: allow to set extra1 to SYSCTL_ONE Muchun Song
2022-03-02 8:37 ` [PATCH v2 3/3] mm: hugetlb: add hugetlb_free_vmemmap sysctl Muchun Song
2022-03-02 21:25 ` Luis Chamberlain
2022-03-03 11:15 ` Muchun Song
2022-03-03 14:59 ` Luis Chamberlain
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=20220302083758.32528-1-songmuchun@bytedance.com \
--to=songmuchun@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=duanxiongchun@bytedance.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=smuchun@gmail.com \
--cc=yzaikin@google.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