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, 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: [PATCH V2 0/5] arm64/mm: Enable HugeTLB migration
Date: Wed, 17 Oct 2018 13:49:17 +0530 [thread overview]
Message-ID: <e1703454-e500-3a1b-35cb-6368dff91f10@arm.com> (raw)
In-Reply-To: <1539316799-6064-1-git-send-email-anshuman.khandual@arm.com>
On 10/12/2018 09:29 AM, 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.
>
> Changes in V2:
>
> - Added a new patch which differentiates migratability and movability
> of huge pages and implements hugepage_movable_supported() function
> as suggested by Michal Hocko.
Hello Andrew/Michal/Mike/Naoya/Catalin,
Just checking for an update. Does this series looks okay ?
- Anshuman
next prev parent reply other threads:[~2018-10-17 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 3:59 [PATCH V2 0/5] arm64/mm: Enable HugeTLB migration Anshuman Khandual
2018-10-12 3:59 ` [PATCH V2 1/5] mm/hugetlb: Enable PUD level huge page migration Anshuman Khandual
2018-10-19 8:09 ` Michal Hocko
2018-10-22 3:01 ` Anshuman Khandual
2018-10-22 7:16 ` Michal Hocko
2018-10-12 3:59 ` [PATCH V2 2/5] mm/hugetlb: Distinguish between migratability and movability Anshuman Khandual
2018-10-19 1:59 ` Naoya Horiguchi
2018-10-19 2:32 ` Anshuman Khandual
2018-10-12 3:59 ` [PATCH V2 3/5] mm/hugetlb: Enable arch specific huge page size support for migration Anshuman Khandual
2018-10-12 3:59 ` [PATCH V2 4/5] arm64/mm: Enable HugeTLB migration Anshuman Khandual
2018-10-12 3:59 ` [PATCH V2 5/5] arm64/mm: Enable HugeTLB migration for contiguous bit HugeTLB pages Anshuman Khandual
2018-10-17 8:19 ` Anshuman Khandual [this message]
2018-10-19 2:01 ` [PATCH V2 0/5] arm64/mm: Enable HugeTLB migration Naoya Horiguchi
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=e1703454-e500-3a1b-35cb-6368dff91f10@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=punit.agrawal@arm.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;
as well as URLs for NNTP newsgroup(s).