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, will.deacon@arm.com,
Steven.Price@arm.com, steve.capper@arm.com,
catalin.marinas@arm.com, mhocko@kernel.org,
akpm@linux-foundation.org, mike.kravetz@oracle.com,
n-horiguchi@ah.jp.nec.com
Subject: Re: [RESEND PATCH V3 0/5] arm64/mm: Enable HugeTLB migration
Date: Thu, 3 Jan 2019 10:34:38 +0530 [thread overview]
Message-ID: <c2fbd55e-4413-1bcf-769c-fd1064e74a2c@arm.com> (raw)
In-Reply-To: <1545121450-1663-1-git-send-email-anshuman.khandual@arm.com>
On 12/18/2018 01:54 PM, Anshuman Khandual wrote:
> 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.
>
> The second patch differentiates between movability and migratability
> aspects of huge pages and implements hugepage_movable_supported() which
> can then be used during allocation to decide whether to place the huge
> page in movable zone or not.
>
> This is just a resend for the previous version (V3) after the rebase
> on current mainline kernel. Also added all the tags previous version
> had received.
>
> Changes in V3:
>
> - Re-ordered patches 1 and 2 per Michal
> - s/Movability/Migratability/ in unmap_and_move_huge_page() per Naoya
>
> Changes in V2: (https://lkml.org/lkml/2018/10/12/190)
>
> - Added a new patch which differentiates migratability and movability
> of huge pages and implements hugepage_movable_supported() function
> as suggested by Michal Hocko.
>
> Anshuman Khandual (5):
> mm/hugetlb: Distinguish between migratability and movability
> 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
>
Hello Andrew,
Just wondering if there are any updates on this series ? Is there something we need to
improve or fix some where in this series for it to get merged. Please do let us know.
Thank you.
- Anshuman
prev parent reply other threads:[~2019-01-03 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 8:24 Anshuman Khandual
2018-12-18 8:24 ` [RESEND PATCH V3 1/5] mm/hugetlb: Distinguish between migratability and movability Anshuman Khandual
2018-12-18 8:24 ` [RESEND PATCH V3 2/5] mm/hugetlb: Enable PUD level huge page migration Anshuman Khandual
2018-12-18 8:24 ` [RESEND PATCH V3 3/5] mm/hugetlb: Enable arch specific huge page size support for migration Anshuman Khandual
2018-12-18 8:24 ` [RESEND PATCH V3 4/5] arm64/mm: Enable HugeTLB migration Anshuman Khandual
2018-12-18 8:24 ` [RESEND PATCH V3 5/5] arm64/mm: Enable HugeTLB migration for contiguous bit HugeTLB pages Anshuman Khandual
2019-01-03 5:04 ` Anshuman Khandual [this message]
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=c2fbd55e-4413-1bcf-769c-fd1064e74a2c@arm.com \
--to=anshuman.khandual@arm.com \
--cc=Steven.Price@arm.com \
--cc=akpm@linux-foundation.org \
--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=steve.capper@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