Re: [PATCH 3/4] mm/hugetlb: make hugetlb migration callback CMA aware

2020-07-15 Thread Vlastimil Babka
On 7/15/20 7:05 AM, js1...@gmail.com wrote: > From: Joonsoo Kim > > new_non_cma_page() in gup.c requires to allocate the new page that is not > on the CMA area. new_non_cma_page() implements it by using allocation > scope APIs. > > However, there is a work-around for hugetlb. Normal hugetlb

Re: [PATCH 3/4] mm/hugetlb: make hugetlb migration callback CMA aware

2020-07-15 Thread Michal Hocko
On Wed 15-07-20 14:05:28, Joonsoo Kim wrote: > From: Joonsoo Kim > > new_non_cma_page() in gup.c requires to allocate the new page that is not > on the CMA area. new_non_cma_page() implements it by using allocation > scope APIs. > > However, there is a work-around for hugetlb. Normal hugetlb

[PATCH 3/4] mm/hugetlb: make hugetlb migration callback CMA aware

2020-07-14 Thread js1304
From: Joonsoo Kim new_non_cma_page() in gup.c requires to allocate the new page that is not on the CMA area. new_non_cma_page() implements it by using allocation scope APIs. However, there is a work-around for hugetlb. Normal hugetlb page allocation API for migration is