Re: [PATCH 3/3] hugetlbfs: don't retry when pool page allocations start to fail

2019-08-05 Thread Mike Kravetz
On 8/5/19 2:28 AM, Vlastimil Babka wrote: > On 8/3/19 12:39 AM, Mike Kravetz wrote: >> When allocating hugetlbfs pool pages via /proc/sys/vm/nr_hugepages, >> the pages will be interleaved between all nodes of the system. If >> nodes are not equal, it is quite possible for one node to fill up >> be

Re: [PATCH 3/3] hugetlbfs: don't retry when pool page allocations start to fail

2019-08-05 Thread Vlastimil Babka
On 8/3/19 12:39 AM, Mike Kravetz wrote: > When allocating hugetlbfs pool pages via /proc/sys/vm/nr_hugepages, > the pages will be interleaved between all nodes of the system. If > nodes are not equal, it is quite possible for one node to fill up > before the others. When this happens, the code st

[PATCH 3/3] hugetlbfs: don't retry when pool page allocations start to fail

2019-08-02 Thread Mike Kravetz
When allocating hugetlbfs pool pages via /proc/sys/vm/nr_hugepages, the pages will be interleaved between all nodes of the system. If nodes are not equal, it is quite possible for one node to fill up before the others. When this happens, the code still attempts to allocate pages from the full nod

Re: [RFC PATCH 3/3] hugetlbfs: don't retry when pool page allocations start to fail

2019-07-31 Thread Mike Kravetz
On 7/31/19 6:23 AM, Vlastimil Babka wrote: > On 7/25/19 7:15 PM, Mike Kravetz wrote: >> On 7/25/19 1:13 AM, Mel Gorman wrote: >>> On Wed, Jul 24, 2019 at 10:50:14AM -0700, Mike Kravetz wrote: >>> >>> set_max_huge_pages can fail the NODEMASK_ALLOC() alloc which you handle >>> *but* in the event of a

Re: [RFC PATCH 3/3] hugetlbfs: don't retry when pool page allocations start to fail

2019-07-31 Thread Vlastimil Babka
On 7/25/19 7:15 PM, Mike Kravetz wrote: > On 7/25/19 1:13 AM, Mel Gorman wrote: >> On Wed, Jul 24, 2019 at 10:50:14AM -0700, Mike Kravetz wrote: >>> When allocating hugetlbfs pool pages via /proc/sys/vm/nr_hugepages, >>> the pages will be interleaved between all nodes of the system. If >>> nodes a

Re: [RFC PATCH 3/3] hugetlbfs: don't retry when pool page allocations start to fail

2019-07-25 Thread Mel Gorman
On Thu, Jul 25, 2019 at 10:15:29AM -0700, Mike Kravetz wrote: > On 7/25/19 1:13 AM, Mel Gorman wrote: > > On Wed, Jul 24, 2019 at 10:50:14AM -0700, Mike Kravetz wrote: > >> When allocating hugetlbfs pool pages via /proc/sys/vm/nr_hugepages, > >> the pages will be interleaved between all nodes of th

Re: [RFC PATCH 3/3] hugetlbfs: don't retry when pool page allocations start to fail

2019-07-25 Thread Mike Kravetz
On 7/25/19 1:13 AM, Mel Gorman wrote: > On Wed, Jul 24, 2019 at 10:50:14AM -0700, Mike Kravetz wrote: >> When allocating hugetlbfs pool pages via /proc/sys/vm/nr_hugepages, >> the pages will be interleaved between all nodes of the system. If >> nodes are not equal, it is quite possible for one nod

Re: [RFC PATCH 3/3] hugetlbfs: don't retry when pool page allocations start to fail

2019-07-25 Thread Mel Gorman
On Wed, Jul 24, 2019 at 10:50:14AM -0700, Mike Kravetz wrote: > When allocating hugetlbfs pool pages via /proc/sys/vm/nr_hugepages, > the pages will be interleaved between all nodes of the system. If > nodes are not equal, it is quite possible for one node to fill up > before the others. When thi

[RFC PATCH 3/3] hugetlbfs: don't retry when pool page allocations start to fail

2019-07-24 Thread Mike Kravetz
When allocating hugetlbfs pool pages via /proc/sys/vm/nr_hugepages, the pages will be interleaved between all nodes of the system. If nodes are not equal, it is quite possible for one node to fill up before the others. When this happens, the code still attempts to allocate pages from the full nod