From: Xie Yisheng <xieyisheng1@huawei.com>
To: <akpm@linux-foundation.org>, <mhocko@kernel.org>
Cc: <guohanjun@huawei.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <will.deacon@arm.com>,
<mhocko@suse.com>, <dave.hansen@intel.com>,
<sudeep.holla@arm.com>, <catalin.marinas@arm.com>,
<mark.rutland@arm.com>, <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <mike.kravetz@oracle.com>,
<n-horiguchi@ah.jp.nec.com>
Subject: [RFC PATCH v2 0/2] arm64/hugetlb: enable gigantic page
Date: Mon, 22 Aug 2016 10:56:41 +0800 [thread overview]
Message-ID: <1471834603-27053-1-git-send-email-xieyisheng1@huawei.com> (raw)
Arm64 supports different size of gigantic page which can be seen from:
commit 084bd29810a5 ("ARM64: mm: HugeTLB support.")
commit 66b3923a1a0f ("arm64: hugetlb: add support for PTE contiguous bit")
So I tried to use this function by adding hugepagesz=1G in kernel
parameters, with CONFIG_CMA=y. However, when I
echo xx > \
/sys/kernel/mm/hugepages/hugepages-1048576kB/nr_hugepages
it failed with the following info:
-bash: echo: write error: Invalid argument
This is a v2 patchset which make gigantic page can be used on arm64,
with CONFIG_CMA=y, or other related configs is enable.
You can see the former discussions at:
https://lkml.org/lkml/2016/8/18/310
Xie Yisheng (2):
mm/hugetlb: Introduce ARCH_HAS_GIGANTIC_PAGE
arm64 Kconfig: Select gigantic page
arch/arm64/Kconfig | 1 +
arch/s390/Kconfig | 1 +
arch/x86/Kconfig | 1 +
fs/Kconfig | 4 ++++
mm/hugetlb.c | 2 +-
5 files changed, 8 insertions(+), 1 deletion(-)
--
1.7.12.4
next reply other threads:[~2016-08-22 2:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 2:56 Xie Yisheng [this message]
2016-08-22 2:56 ` [RFC PATCH v2 1/2] mm/hugetlb: Introduce ARCH_HAS_GIGANTIC_PAGE Xie Yisheng
2016-08-22 8:01 ` Michal Hocko
2016-08-22 10:37 ` Yisheng Xie
2016-08-22 2:56 ` [RFC PATCH v2 2/2] arm64 Kconfig: Select gigantic page Xie Yisheng
2016-08-22 8:03 ` Michal Hocko
2016-08-22 10:00 ` Catalin Marinas
2016-08-22 11:33 ` Yisheng Xie
2016-08-22 10:21 ` Catalin Marinas
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=1471834603-27053-1-git-send-email-xieyisheng1@huawei.com \
--to=xieyisheng1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@intel.com \
--cc=guohanjun@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will.deacon@arm.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).