Re: [RFC PATCH 3/5] mm, hugetlb: do not rely on overcommit limit during migration

2017-12-14 Thread Mike Kravetz
On 12/13/2017 11:40 PM, Michal Hocko wrote: > On Wed 13-12-17 15:35:33, Mike Kravetz wrote: >> On 12/04/2017 06:01 AM, Michal Hocko wrote: > [...] >>> Before migration >>> /sys/devices/system/node/node0/hugepages/hugepages-2048kB/free_hugepages:0 >>>

Re: [RFC PATCH 3/5] mm, hugetlb: do not rely on overcommit limit during migration

2017-12-14 Thread Mike Kravetz
On 12/13/2017 11:40 PM, Michal Hocko wrote: > On Wed 13-12-17 15:35:33, Mike Kravetz wrote: >> On 12/04/2017 06:01 AM, Michal Hocko wrote: > [...] >>> Before migration >>> /sys/devices/system/node/node0/hugepages/hugepages-2048kB/free_hugepages:0 >>>

Re: [RFC PATCH 3/5] mm, hugetlb: do not rely on overcommit limit during migration

2017-12-13 Thread Michal Hocko
On Wed 13-12-17 15:35:33, Mike Kravetz wrote: > On 12/04/2017 06:01 AM, Michal Hocko wrote: [...] > > Before migration > > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/free_hugepages:0 > > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages:1 > >

Re: [RFC PATCH 3/5] mm, hugetlb: do not rely on overcommit limit during migration

2017-12-13 Thread Michal Hocko
On Wed 13-12-17 15:35:33, Mike Kravetz wrote: > On 12/04/2017 06:01 AM, Michal Hocko wrote: [...] > > Before migration > > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/free_hugepages:0 > > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages:1 > >

Re: [RFC PATCH 3/5] mm, hugetlb: do not rely on overcommit limit during migration

2017-12-13 Thread Mike Kravetz
On 12/04/2017 06:01 AM, Michal Hocko wrote: > From: Michal Hocko > > hugepage migration relies on __alloc_buddy_huge_page to get a new page. > This has 2 main disadvantages. > 1) it doesn't allow to migrate any huge page if the pool is used > completely which is not an

Re: [RFC PATCH 3/5] mm, hugetlb: do not rely on overcommit limit during migration

2017-12-13 Thread Mike Kravetz
On 12/04/2017 06:01 AM, Michal Hocko wrote: > From: Michal Hocko > > hugepage migration relies on __alloc_buddy_huge_page to get a new page. > This has 2 main disadvantages. > 1) it doesn't allow to migrate any huge page if the pool is used > completely which is not an exceptional case as the

[RFC PATCH 3/5] mm, hugetlb: do not rely on overcommit limit during migration

2017-12-04 Thread Michal Hocko
From: Michal Hocko hugepage migration relies on __alloc_buddy_huge_page to get a new page. This has 2 main disadvantages. 1) it doesn't allow to migrate any huge page if the pool is used completely which is not an exceptional case as the pool is static and unused memory is just

[RFC PATCH 3/5] mm, hugetlb: do not rely on overcommit limit during migration

2017-12-04 Thread Michal Hocko
From: Michal Hocko hugepage migration relies on __alloc_buddy_huge_page to get a new page. This has 2 main disadvantages. 1) it doesn't allow to migrate any huge page if the pool is used completely which is not an exceptional case as the pool is static and unused memory is just wasted. 2) it