From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: suzuki.poulose@arm.com, punit.agrawal@arm.com,
will.deacon@arm.com, Steven.Price@arm.com,
catalin.marinas@arm.com, mhocko@kernel.org,
mike.kravetz@oracle.com, n-horiguchi@ah.jp.nec.com
Subject: [PATCH 0/4] arm64/mm: Enable HugeTLB migration
Date: Tue, 2 Oct 2018 17:45:27 +0530 [thread overview]
Message-ID: <1538482531-26883-1-git-send-email-anshuman.khandual@arm.com> (raw)
This patch series enables HugeTLB migration support for all supported
huge page sizes at all levels including contiguous bit implementation.
Following HugeTLB migration support matrix has been enabled with this
patch series. All permutations have been tested except for the 16GB.
CONT PTE PMD CONT PMD PUD
-------- --- -------- ---
4K: 64K 2M 32M 1G
16K: 2M 32M 1G
64K: 2M 512M 16G
First the series adds migration support for PUD based huge pages. It
then adds a platform specific hook to query an architecture if a
given huge page size is supported for migration while also providing
a default fallback option preserving the existing semantics which just
checks for (PMD|PUD|PGDIR)_SHIFT macros. The last two patches enables
HugeTLB migration on arm64 and subscribe to this new platform specific
hook by defining an override.
Anshuman Khandual (4):
mm/hugetlb: Enable PUD level huge page migration
mm/hugetlb: Enable arch specific huge page size support for migration
arm64/mm: Enable HugeTLB migration
arm64/mm: Enable HugeTLB migration for contiguous bit HugeTLB pages
arch/arm64/Kconfig | 4 ++++
arch/arm64/include/asm/hugetlb.h | 5 +++++
arch/arm64/mm/hugetlbpage.c | 20 ++++++++++++++++++++
include/linux/hugetlb.h | 18 +++++++++++++++---
4 files changed, 44 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2018-10-02 12:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 12:15 Anshuman Khandual [this message]
2018-10-02 12:15 ` [PATCH 1/4] mm/hugetlb: Enable PUD level huge page migration Anshuman Khandual
2018-10-02 12:38 ` Suzuki K Poulose
2018-10-02 12:56 ` Anshuman Khandual
2018-10-03 10:22 ` Suzuki K Poulose
2018-10-03 11:10 ` Anshuman Khandual
2018-10-03 11:17 ` Suzuki K Poulose
2018-10-03 11:27 ` Michal Hocko
2018-10-02 12:39 ` Michal Hocko
2018-10-03 2:16 ` Anshuman Khandual
2018-10-03 6:58 ` Michal Hocko
2018-10-03 9:58 ` Anshuman Khandual
2018-10-03 10:59 ` Michal Hocko
2018-10-03 11:37 ` Anshuman Khandual
2018-10-03 11:48 ` Michal Hocko
2018-10-03 13:06 ` Anshuman Khandual
2018-10-03 13:36 ` Michal Hocko
2018-10-05 7:34 ` Anshuman Khandual
2018-10-09 14:14 ` Michal Hocko
2018-10-10 3:09 ` Anshuman Khandual
2018-10-10 9:39 ` Michal Hocko
2018-10-11 3:16 ` Anshuman Khandual
2018-10-02 12:15 ` [PATCH 2/4] mm/hugetlb: Enable arch specific huge page size support for migration Anshuman Khandual
2018-10-02 12:15 ` [PATCH 3/4] arm64/mm: Enable HugeTLB migration Anshuman Khandual
2018-10-02 12:15 ` [PATCH 4/4] arm64/mm: Enable HugeTLB migration for contiguous bit HugeTLB pages Anshuman Khandual
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=1538482531-26883-1-git-send-email-anshuman.khandual@arm.com \
--to=anshuman.khandual@arm.com \
--cc=Steven.Price@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=punit.agrawal@arm.com \
--cc=suzuki.poulose@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).