Re: [RFC PATCH 5/5] mm, hugetlb: further simplify hugetlb allocation API

2017-12-14 Thread Mike Kravetz
On 12/04/2017 06:01 AM, Michal Hocko wrote: > From: Michal Hocko > > Hugetlb allocator has several layer of allocation functions depending > and the purpose of the allocation. There are two allocators depending > on whether the page can be allocated from the page allocator or we

Re: [RFC PATCH 5/5] mm, hugetlb: further simplify hugetlb allocation API

2017-12-14 Thread Mike Kravetz
On 12/04/2017 06:01 AM, Michal Hocko wrote: > From: Michal Hocko > > Hugetlb allocator has several layer of allocation functions depending > and the purpose of the allocation. There are two allocators depending > on whether the page can be allocated from the page allocator or we need > a

[RFC PATCH 5/5] mm, hugetlb: further simplify hugetlb allocation API

2017-12-04 Thread Michal Hocko
From: Michal Hocko Hugetlb allocator has several layer of allocation functions depending and the purpose of the allocation. There are two allocators depending on whether the page can be allocated from the page allocator or we need a contiguous allocator. This is currently

[RFC PATCH 5/5] mm, hugetlb: further simplify hugetlb allocation API

2017-12-04 Thread Michal Hocko
From: Michal Hocko Hugetlb allocator has several layer of allocation functions depending and the purpose of the allocation. There are two allocators depending on whether the page can be allocated from the page allocator or we need a contiguous allocator. This is currently opencoded in