Re: [PATCH 1/5] mm, page_alloc: Spread allocations across zones before introducing fragmentation

2018-11-26 Thread Vlastimil Babka
On 11/23/18 12:45 PM, Mel Gorman wrote: ... > Fault latencies are slightly reduced while allocation success rates remain > at zero as this configuration does not make any special effort to allocate > THP and fio is heavily active at the time and either filling memory or > keeping pages resident.

[PATCH 1/5] mm, page_alloc: Spread allocations across zones before introducing fragmentation

2018-11-23 Thread Mel Gorman
The page allocator zone lists are iterated based on the watermarks of each zone which does not take anti-fragmentation into account. On x86, node 0 may have multiple zones while other nodes have one zone. A consequence is that tasks running on node 0 may fragment ZONE_NORMAL even though ZONE_DMA32

[PATCH 1/5] mm, page_alloc: Spread allocations across zones before introducing fragmentation

2018-11-07 Thread Mel Gorman
The page allocator zone lists are iterated based on the watermarks of each zone which does not take anti-fragmentation into account. On x86, node 0 may have multiple zones while other nodes have one zone. A consequence is that tasks running on node 0 may fragment ZONE_NORMAL even though ZONE_DMA32

[PATCH 1/5] mm, page_alloc: Spread allocations across zones before introducing fragmentation

2018-10-31 Thread Mel Gorman
The page allocator zone lists are iterated based on the watermarks of each zone which does not take anti-fragmentation into account. On x86, node 0 may have multiple zones while other nodes have one zone. A consequence is that tasks running on node 0 may fragment ZONE_NORMAL even though ZONE_DMA32