[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4c952f57-41d4-bd51-700b-554c1cf9bf6f@oracle.com>
Date: Thu, 21 May 2020 14:43:27 -0700
From: Mike Kravetz <mike.kravetz@...cle.com>
To: js1304@...il.com, Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
kernel-team@....com, Vlastimil Babka <vbabka@...e.cz>,
Christoph Hellwig <hch@...radead.org>,
Roman Gushchin <guro@...com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Michal Hocko <mhocko@...e.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>
Subject: Re: [PATCH 05/11] mm/hugetlb: make hugetlb migration target
allocation APIs CMA aware
On 5/17/20 6:20 PM, js1304@...il.com wrote:
> From: Joonsoo Kim <iamjoonsoo.kim@....com>
>
> There is a user who do not want to use CMA memory for migration. Until
> now, it is implemented by caller side but it's not optimal since there
> is limited information on caller. This patch implements it on callee side
> to get better result.
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@....com>
Thank you!
Avoiding CMA works much better with this new skip_cma field.
Acked-by: Mike Kravetz <mike.kravetz@...cle.com>
--
Mike Kravetz
Powered by blists - more mailing lists