[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181108103340.ajeg566spidprzzk@capper-debian.cambridge.arm.com>
Date: Thu, 8 Nov 2018 10:33:52 +0000
From: Steve Capper <Steve.Capper@....com>
To: Anshuman Khandual <Anshuman.Khandual@....com>
CC: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Suzuki Poulose <Suzuki.Poulose@....com>,
Punit Agrawal <Punit.Agrawal@....com>,
Will Deacon <Will.Deacon@....com>,
Steven Price <Steven.Price@....com>,
Catalin Marinas <Catalin.Marinas@....com>,
"mhocko@...nel.org" <mhocko@...nel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"mike.kravetz@...cle.com" <mike.kravetz@...cle.com>,
"n-horiguchi@...jp.nec.com" <n-horiguchi@...jp.nec.com>,
nd <nd@....com>
Subject: Re: [PATCH V3 1/5] mm/hugetlb: Distinguish between migratability and
movability
Hi Anshuman,
On Tue, Oct 23, 2018 at 06:31:57PM +0530, Anshuman Khandual wrote:
> During huge page allocation it's migratability is checked to determine if
> it should be placed under movable zones with GFP_HIGHUSER_MOVABLE. But the
> movability aspect of the huge page could depend on other factors than just
> migratability. Movability in itself is a distinct property which should not
> be tied with migratability alone.
>
> This differentiates these two and implements an enhanced movability check
> which also considers huge page size to determine if it is feasible to be
> placed under a movable zone. At present it just checks for gigantic pages
> but going forward it can incorporate other enhanced checks.
>
> Reviewed-by: Naoya Horiguchi <n-horiguchi@...jp.nec.com>
> Suggested-by: Michal Hocko <mhocko@...nel.org>
> Signed-off-by: Anshuman Khandual <anshuman.khandual@....com>
FWIW:
Reviewed-by: Steve Capper <steve.capper@....com>
Powered by blists - more mailing lists