| Message ID | 20181121101414.21301-5-mgorman@techsingularity.net (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | Fragmentation avoidance improvements v4 | expand |
On 11/21/18 11:14 AM, Mel Gorman wrote: > An event that potentially causes external fragmentation problems has > already been described but there are degrees of severity. A "serious" > event is defined as one that steals a contiguous range of pages of an order > lower than fragment_stall_order (PAGE_ALLOC_COSTLY_ORDER by default). If a > movable allocation request that is allowed to sleep needs to steal a small > block then it schedules until kswapd makes progress or a timeout passes. > The watermarks are also boosted slightly faster so that kswapd makes > greater effort to reclaim enough pages to avoid the fragmentation event. > > This stall is not guaranteed to avoid serious fragmentation events. > If memory pressure is high enough, the pages freed by kswapd may be > reallocated or the free pages may not be in pageblocks that contain > only movable pages. Furthermore an allocation request that cannot stall > (e.g. atomic allocations) or unmovable/reclaimable allocations will still > proceed without stalling. Not doing this for unmovable/reclaimable allocations is kinda disadvantage? > ============================================================== > > +fragment_stall_order > + > +External fragmentation control is managed on a pageblock level where the > +page allocator tries to avoid mixing pages of different mobility within page > +blocks (e.g. order 9 on 64-bit x86). If external fragmentation is perfectly > +controlled then a THP allocation will often succeed up to the number of > +movable pageblocks in the system as reported by /proc/pagetypeinfo. > + > +When memory is low, the system may have to mix pageblocks and will wake > +kswapd to try control future fragmentation. fragment_stall_order controls if > +the allocating task will stall if possible until kswapd makes some progress > +in preference to fragmenting the system. This incurs a small stall penalty > +in exchange for future success at allocating huge pages. If the stalls > +are undesirable and high-order allocations are irrelevant then this can > +be disabled by writing 0 to the tunable. Writing the pageblock order will > +strongly (but not perfectly) control external fragmentation. > + > +The default will stall for fragmenting allocations smaller than the > +PAGE_ALLOC_COSTLY_ORDER (defined as order-3 at the time of writing). Perhaps be more explicit that steals of orders strictly lower than given value will stall? So for the default order-3, the sysctl value is 4, which might confuse somebody. > + > @@ -2130,9 +2131,10 @@ static bool can_steal_fallback(unsigned int order, int start_mt) > return false; > } > > + > +static void stall_fragmentation(struct zone *pzone) > +{ > + DEFINE_WAIT(wait); > + long remaining = 0; > + long timeout = HZ/50; > + pg_data_t *pgdat = pzone->zone_pgdat; > + > + if (current->flags & PF_MEMALLOC) > + return; > + > + boost_watermark(pzone, true); Should zone->lock be taken around this to make watermark_boost adjustment safe? Similar to balance_pgdat(). > + prepare_to_wait(&pgdat->pfmemalloc_wait, &wait, TASK_INTERRUPTIBLE); > + if (waitqueue_active(&pgdat->kswapd_wait)) > + wake_up_interruptible(&pgdat->kswapd_wait); > + remaining = schedule_timeout(timeout); > + finish_wait(&pgdat->pfmemalloc_wait, &wait); > + if (remaining != timeout) { > + trace_mm_fragmentation_stall(pgdat->node_id, > + jiffies_to_usecs(timeout - remaining)); > + count_vm_event(FRAGMENTSTALL); > + } > } > > @@ -4186,6 +4234,14 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order, > */ > alloc_flags = gfp_to_alloc_flags(gfp_mask); > > + /* > + * Consider stalling on heavy for movable allocations in preference to > + * fragmenting unmovable/reclaimable pageblocks. > + */ > + if ((gfp_mask & (__GFP_MOVABLE|__GFP_DIRECT_RECLAIM)) == > + (__GFP_MOVABLE|__GFP_DIRECT_RECLAIM)) > + alloc_flags |= ALLOC_FRAGMENT_STALL; Surprised that this only has effect in the slowpath, i.e. when watermarks are below 'low'. If it's intended (to not stall that much I suppose) maybe explain the rationale in the changelog? Thanks for the series, Mel, hope the results are still optimistic after some of the fixes that might unfortunately limit its impact :) Vlastimil
On Thu, Nov 22, 2018 at 06:02:10PM +0100, Vlastimil Babka wrote: > On 11/21/18 11:14 AM, Mel Gorman wrote: > > An event that potentially causes external fragmentation problems has > > already been described but there are degrees of severity. A "serious" > > event is defined as one that steals a contiguous range of pages of an order > > lower than fragment_stall_order (PAGE_ALLOC_COSTLY_ORDER by default). If a > > movable allocation request that is allowed to sleep needs to steal a small > > block then it schedules until kswapd makes progress or a timeout passes. > > The watermarks are also boosted slightly faster so that kswapd makes > > greater effort to reclaim enough pages to avoid the fragmentation event. > > > > This stall is not guaranteed to avoid serious fragmentation events. > > If memory pressure is high enough, the pages freed by kswapd may be > > reallocated or the free pages may not be in pageblocks that contain > > only movable pages. Furthermore an allocation request that cannot stall > > (e.g. atomic allocations) or unmovable/reclaimable allocations will still > > proceed without stalling. > > Not doing this for unmovable/reclaimable allocations is kinda disadvantage? > Yes, but this series is primarily aimed at when movable allocations are causing the fragmentation. We stall so that there are compaction targets due to reclaimed pages. The same does not apply to unmovable and reclaimable pages because they cannot compact so sure, we can stall, but I cannot see how it would help. > > ============================================================== > > > > +fragment_stall_order > > + > > +External fragmentation control is managed on a pageblock level where the > > +page allocator tries to avoid mixing pages of different mobility within page > > +blocks (e.g. order 9 on 64-bit x86). If external fragmentation is perfectly > > +controlled then a THP allocation will often succeed up to the number of > > +movable pageblocks in the system as reported by /proc/pagetypeinfo. > > + > > +When memory is low, the system may have to mix pageblocks and will wake > > +kswapd to try control future fragmentation. fragment_stall_order controls if > > +the allocating task will stall if possible until kswapd makes some progress > > +in preference to fragmenting the system. This incurs a small stall penalty > > +in exchange for future success at allocating huge pages. If the stalls > > +are undesirable and high-order allocations are irrelevant then this can > > +be disabled by writing 0 to the tunable. Writing the pageblock order will > > +strongly (but not perfectly) control external fragmentation. > > + > > +The default will stall for fragmenting allocations smaller than the > > +PAGE_ALLOC_COSTLY_ORDER (defined as order-3 at the time of writing). > > Perhaps be more explicit that steals of orders strictly lower than given > value will stall? So for the default order-3, the sysctl value is 4, > which might confuse somebody. > I'll clarify it. > > + > > @@ -2130,9 +2131,10 @@ static bool can_steal_fallback(unsigned int order, int start_mt) > > return false; > > } > > > > + > > +static void stall_fragmentation(struct zone *pzone) > > +{ > > + DEFINE_WAIT(wait); > > + long remaining = 0; > > + long timeout = HZ/50; > > + pg_data_t *pgdat = pzone->zone_pgdat; > > + > > + if (current->flags & PF_MEMALLOC) > > + return; > > + > > + boost_watermark(pzone, true); > > Should zone->lock be taken around this to make watermark_boost > adjustment safe? Similar to balance_pgdat(). > Yeah, that was a relatively late adjustment. The risk is low but it's possible best to be safe. I'm not super-keen that zone->lock protects this but that lock already protects more than it should and there is little motivation to split it just yet. > > + prepare_to_wait(&pgdat->pfmemalloc_wait, &wait, TASK_INTERRUPTIBLE); > > + if (waitqueue_active(&pgdat->kswapd_wait)) > > + wake_up_interruptible(&pgdat->kswapd_wait); > > + remaining = schedule_timeout(timeout); > > + finish_wait(&pgdat->pfmemalloc_wait, &wait); > > + if (remaining != timeout) { > > + trace_mm_fragmentation_stall(pgdat->node_id, > > + jiffies_to_usecs(timeout - remaining)); > > + count_vm_event(FRAGMENTSTALL); > > + } > > } > > > > > @@ -4186,6 +4234,14 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order, > > */ > > alloc_flags = gfp_to_alloc_flags(gfp_mask); > > > > + /* > > + * Consider stalling on heavy for movable allocations in preference to > > + * fragmenting unmovable/reclaimable pageblocks. > > + */ > > + if ((gfp_mask & (__GFP_MOVABLE|__GFP_DIRECT_RECLAIM)) == > > + (__GFP_MOVABLE|__GFP_DIRECT_RECLAIM)) > > + alloc_flags |= ALLOC_FRAGMENT_STALL; > > Surprised that this only has effect in the slowpath, i.e. when > watermarks are below 'low'. If it's intended (to not stall that much I > suppose) maybe explain the rationale in the changelog? > Well, it's the same path when stalls can happen on direct reclaim so I didn't think it needed to be explicitly called out. The slowpath is also the "we can stall if the context allows" path so this is checking that it's a compatible cont3xt. > Thanks for the series, Mel, hope the results are still optimistic after > some of the fixes that might unfortunately limit its impact :) > Preliminary results indicate they are slightly worse but slightly worse than 90+% is still better than nothing so I'm reasonably optimistic! Thanks for the careful review and catching a lot of issues!
diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt index 4dff1b75229b..7d4f41bf7902 100644 --- a/Documentation/sysctl/vm.txt +++ b/Documentation/sysctl/vm.txt @@ -31,6 +31,7 @@ files can be found in mm/swap.c. - dirty_writeback_centisecs - drop_caches - extfrag_threshold +- fragment_stall_order - hugetlb_shm_group - laptop_mode - legacy_va_layout @@ -275,6 +276,28 @@ any throttling. ============================================================== +fragment_stall_order + +External fragmentation control is managed on a pageblock level where the +page allocator tries to avoid mixing pages of different mobility within page +blocks (e.g. order 9 on 64-bit x86). If external fragmentation is perfectly +controlled then a THP allocation will often succeed up to the number of +movable pageblocks in the system as reported by /proc/pagetypeinfo. + +When memory is low, the system may have to mix pageblocks and will wake +kswapd to try control future fragmentation. fragment_stall_order controls if +the allocating task will stall if possible until kswapd makes some progress +in preference to fragmenting the system. This incurs a small stall penalty +in exchange for future success at allocating huge pages. If the stalls +are undesirable and high-order allocations are irrelevant then this can +be disabled by writing 0 to the tunable. Writing the pageblock order will +strongly (but not perfectly) control external fragmentation. + +The default will stall for fragmenting allocations smaller than the +PAGE_ALLOC_COSTLY_ORDER (defined as order-3 at the time of writing). + +============================================================== + hugetlb_shm_group hugetlb_shm_group contains group id that is allowed to create SysV diff --git a/include/linux/mm.h b/include/linux/mm.h index 2c4c69508413..2b72de790ef9 100644 --- a/include/linux/mm.h +++ b/include/linux/mm.h @@ -2204,6 +2204,7 @@ extern void zone_pcp_reset(struct zone *zone); extern int min_free_kbytes; extern int watermark_boost_factor; extern int watermark_scale_factor; +extern int fragment_stall_order; /* nommu.c */ extern atomic_long_t mmap_pages_allocated; diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h index d352c1dab486..cffec484ac8a 100644 --- a/include/linux/mmzone.h +++ b/include/linux/mmzone.h @@ -890,6 +890,8 @@ int watermark_boost_factor_sysctl_handler(struct ctl_table *, int, void __user *, size_t *, loff_t *); int watermark_scale_factor_sysctl_handler(struct ctl_table *, int, void __user *, size_t *, loff_t *); +int fragment_stall_order_sysctl_handler(struct ctl_table *, int, + void __user *, size_t *, loff_t *); extern int sysctl_lowmem_reserve_ratio[MAX_NR_ZONES]; int lowmem_reserve_ratio_sysctl_handler(struct ctl_table *, int, void __user *, size_t *, loff_t *); diff --git a/include/linux/vm_event_item.h b/include/linux/vm_event_item.h index 47a3441cf4c4..7661abe5236e 100644 --- a/include/linux/vm_event_item.h +++ b/include/linux/vm_event_item.h @@ -43,6 +43,7 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT, PAGEOUTRUN, PGROTATED, DROP_PAGECACHE, DROP_SLAB, OOM_KILL, + FRAGMENTSTALL, #ifdef CONFIG_NUMA_BALANCING NUMA_PTE_UPDATES, NUMA_HUGE_PTE_UPDATES, diff --git a/include/trace/events/kmem.h b/include/trace/events/kmem.h index eb57e3037deb..caadd8681ac5 100644 --- a/include/trace/events/kmem.h +++ b/include/trace/events/kmem.h @@ -315,6 +315,27 @@ TRACE_EVENT(mm_page_alloc_extfrag, __entry->change_ownership) ); +TRACE_EVENT(mm_fragmentation_stall, + + TP_PROTO(int nid, unsigned long duration), + + TP_ARGS(nid, duration), + + TP_STRUCT__entry( + __field( int, nid ) + __field( unsigned long, duration ) + ), + + TP_fast_assign( + __entry->nid = nid; + __entry->duration = duration + ), + + TP_printk("nid=%d duration=%lu", + __entry->nid, + __entry->duration) +); + #endif /* _TRACE_KMEM_H */ /* This part must be outside protection */ diff --git a/kernel/sysctl.c b/kernel/sysctl.c index 1825f712e73b..eb09c79ddbef 100644 --- a/kernel/sysctl.c +++ b/kernel/sysctl.c @@ -126,6 +126,7 @@ static int zero; static int __maybe_unused one = 1; static int __maybe_unused two = 2; static int __maybe_unused four = 4; +static int __maybe_unused max_order = MAX_ORDER; static unsigned long one_ul = 1; static int one_hundred = 100; static int one_thousand = 1000; @@ -1479,6 +1480,15 @@ static struct ctl_table vm_table[] = { .extra1 = &one, .extra2 = &one_thousand, }, + { + .procname = "fragment_stall_order", + .data = &fragment_stall_order, + .maxlen = sizeof(fragment_stall_order), + .mode = 0644, + .proc_handler = fragment_stall_order_sysctl_handler, + .extra1 = &zero, + .extra2 = &max_order, + }, { .procname = "percpu_pagelist_fraction", .data = &percpu_pagelist_fraction, diff --git a/mm/internal.h b/mm/internal.h index 544355156c92..5506a4596d59 100644 --- a/mm/internal.h +++ b/mm/internal.h @@ -489,6 +489,7 @@ unsigned long reclaim_clean_pages_from_list(struct zone *zone, #else #define ALLOC_NOFRAGMENT 0x0 #endif +#define ALLOC_FRAGMENT_STALL 0x200 /* stall if fragmenting heavily */ enum ttu_flags; struct tlbflush_unmap_batch; diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 04b29228e9f0..e8b0691e8971 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -265,6 +265,7 @@ int min_free_kbytes = 1024; int user_min_free_kbytes = -1; int watermark_boost_factor __read_mostly = 15000; int watermark_scale_factor = 10; +int fragment_stall_order __read_mostly = (PAGE_ALLOC_COSTLY_ORDER + 1); static unsigned long nr_kernel_pages __meminitdata; static unsigned long nr_all_pages __meminitdata; @@ -2130,9 +2131,10 @@ static bool can_steal_fallback(unsigned int order, int start_mt) return false; } -static inline void boost_watermark(struct zone *zone) +static inline void boost_watermark(struct zone *zone, bool fast_boost) { unsigned long max_boost; + unsigned long nr; if (!watermark_boost_factor) return; @@ -2140,9 +2142,36 @@ static inline void boost_watermark(struct zone *zone) max_boost = mult_frac(wmark_pages(zone, WMARK_HIGH), watermark_boost_factor, 10000); max_boost = max(pageblock_nr_pages, max_boost); + nr = pageblock_nr_pages; - zone->watermark_boost = min(zone->watermark_boost + pageblock_nr_pages, - max_boost); + /* Scale relative to the MIGRATE_PCPTYPES similar to min_free_kbytes */ + if (fast_boost) + nr += pageblock_nr_pages * (MIGRATE_PCPTYPES << 1); + + zone->watermark_boost = min(zone->watermark_boost + nr, max_boost); +} + +static void stall_fragmentation(struct zone *pzone) +{ + DEFINE_WAIT(wait); + long remaining = 0; + long timeout = HZ/50; + pg_data_t *pgdat = pzone->zone_pgdat; + + if (current->flags & PF_MEMALLOC) + return; + + boost_watermark(pzone, true); + prepare_to_wait(&pgdat->pfmemalloc_wait, &wait, TASK_INTERRUPTIBLE); + if (waitqueue_active(&pgdat->kswapd_wait)) + wake_up_interruptible(&pgdat->kswapd_wait); + remaining = schedule_timeout(timeout); + finish_wait(&pgdat->pfmemalloc_wait, &wait); + if (remaining != timeout) { + trace_mm_fragmentation_stall(pgdat->node_id, + jiffies_to_usecs(timeout - remaining)); + count_vm_event(FRAGMENTSTALL); + } } /* @@ -2153,8 +2182,9 @@ static inline void boost_watermark(struct zone *zone) * of pages are free or compatible, we can change migratetype of the pageblock * itself, so pages freed in the future will be put on the correct free list. */ -static void steal_suitable_fallback(struct zone *zone, struct page *page, - int start_type, bool whole_block) +static bool steal_suitable_fallback(struct zone *zone, struct page *page, + int start_type, bool whole_block, + unsigned int alloc_flags) { unsigned int current_order = page_order(page); struct free_area *area; @@ -2181,9 +2211,14 @@ static void steal_suitable_fallback(struct zone *zone, struct page *page, * likelihood of future fallbacks. Wake kswapd now as the node * may be balanced overall and kswapd will not wake naturally. */ - boost_watermark(zone); + boost_watermark(zone, false); wakeup_kswapd(zone, 0, 0, zone_idx(zone)); + if ((alloc_flags & ALLOC_FRAGMENT_STALL) && + current_order < fragment_stall_order) { + return false; + } + /* We are not allowed to try stealing from the whole block */ if (!whole_block) goto single_page; @@ -2224,11 +2259,12 @@ static void steal_suitable_fallback(struct zone *zone, struct page *page, page_group_by_mobility_disabled) set_pageblock_migratetype(page, start_type); - return; + return true; single_page: area = &zone->free_area[current_order]; list_move(&page->lru, &area->free_list[start_type]); + return true; } /* @@ -2467,13 +2503,14 @@ __rmqueue_fallback(struct zone *zone, int order, int start_migratetype, page = list_first_entry(&area->free_list[fallback_mt], struct page, lru); - steal_suitable_fallback(zone, page, start_migratetype, can_steal); + if (!steal_suitable_fallback(zone, page, start_migratetype, can_steal, + alloc_flags)) + return false; trace_mm_page_alloc_extfrag(page, order, current_order, start_migratetype, fallback_mt); return true; - } /* @@ -3340,9 +3377,11 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned int order, int alloc_flags, const struct alloc_context *ac) { struct zoneref *z = ac->preferred_zoneref; + struct zone *pzone = z->zone; struct zone *zone; struct pglist_data *last_pgdat_dirty_limit = NULL; bool no_fallback; + bool fragment_stall; retry: /* @@ -3350,6 +3389,8 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned int order, int alloc_flags, * See also __cpuset_node_allowed() comment in kernel/cpuset.c. */ no_fallback = alloc_flags & ALLOC_NOFRAGMENT; + fragment_stall = alloc_flags & ALLOC_FRAGMENT_STALL; + for_next_zone_zonelist_nodemask(zone, z, ac->zonelist, ac->high_zoneidx, ac->nodemask) { struct page *page; @@ -3388,7 +3429,7 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned int order, int alloc_flags, } } - if (no_fallback) { + if (no_fallback || fragment_stall) { int local_nid; /* @@ -3396,9 +3437,12 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned int order, int alloc_flags, * fragmenting fallbacks. Locality is more important * than fragmentation avoidance. */ - local_nid = zone_to_nid(ac->preferred_zoneref->zone); + local_nid = zone_to_nid(pzone); if (zone_to_nid(zone) != local_nid) { + if (fragment_stall) + stall_fragmentation(pzone); alloc_flags &= ~ALLOC_NOFRAGMENT; + alloc_flags &= ~ALLOC_FRAGMENT_STALL; goto retry; } } @@ -3474,8 +3518,12 @@ get_page_from_freelist(gfp_t gfp_mask, unsigned int order, int alloc_flags, * It's possible on a UMA machine to get through all zones that are * fragmented. If avoiding fragmentation, reset and try again */ - if (no_fallback) { + if (no_fallback || fragment_stall) { + if (fragment_stall) + stall_fragmentation(pzone); + alloc_flags &= ~ALLOC_NOFRAGMENT; + alloc_flags &= ~ALLOC_FRAGMENT_STALL; goto retry; } @@ -4186,6 +4234,14 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order, */ alloc_flags = gfp_to_alloc_flags(gfp_mask); + /* + * Consider stalling on heavy for movable allocations in preference to + * fragmenting unmovable/reclaimable pageblocks. + */ + if ((gfp_mask & (__GFP_MOVABLE|__GFP_DIRECT_RECLAIM)) == + (__GFP_MOVABLE|__GFP_DIRECT_RECLAIM)) + alloc_flags |= ALLOC_FRAGMENT_STALL; + /* * We need to recalculate the starting point for the zonelist iterator * because we might have used different nodemask in the fast path, or @@ -4207,6 +4263,7 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order, page = get_page_from_freelist(gfp_mask, order, alloc_flags, ac); if (page) goto got_pg; + alloc_flags &= ~ALLOC_FRAGMENT_STALL; /* * For costly allocations, try direct compaction first, as it's likely @@ -7583,6 +7640,18 @@ int watermark_boost_factor_sysctl_handler(struct ctl_table *table, int write, return 0; } +int fragment_stall_order_sysctl_handler(struct ctl_table *table, int write, + void __user *buffer, size_t *length, loff_t *ppos) +{ + int rc; + + rc = proc_dointvec_minmax(table, write, buffer, length, ppos); + if (rc) + return rc; + + return 0; +} + int watermark_scale_factor_sysctl_handler(struct ctl_table *table, int write, void __user *buffer, size_t *length, loff_t *ppos) { diff --git a/mm/vmstat.c b/mm/vmstat.c index 9c624595e904..6cc7755c6eb1 100644 --- a/mm/vmstat.c +++ b/mm/vmstat.c @@ -1211,6 +1211,7 @@ const char * const vmstat_text[] = { "drop_pagecache", "drop_slab", "oom_kill", + "fragment_stall", #ifdef CONFIG_NUMA_BALANCING "numa_pte_updates",
An event that potentially causes external fragmentation problems has already been described but there are degrees of severity. A "serious" event is defined as one that steals a contiguous range of pages of an order lower than fragment_stall_order (PAGE_ALLOC_COSTLY_ORDER by default). If a movable allocation request that is allowed to sleep needs to steal a small block then it schedules until kswapd makes progress or a timeout passes. The watermarks are also boosted slightly faster so that kswapd makes greater effort to reclaim enough pages to avoid the fragmentation event. This stall is not guaranteed to avoid serious fragmentation events. If memory pressure is high enough, the pages freed by kswapd may be reallocated or the free pages may not be in pageblocks that contain only movable pages. Furthermore an allocation request that cannot stall (e.g. atomic allocations) or unmovable/reclaimable allocations will still proceed without stalling. The worst-case scenario for stalling is a combination of both high memory pressure where kswapd is having trouble keeping free pages over the pfmemalloc_reserve and movable allocations are fragmenting memory. In this case, an allocation request may sleep for longer. There are both vmstats to identify stalls are happening and a tracepoint to quantify what the stall durations are. Note that the granularity of the stall detection is a jiffy so the delay accounting is not precise. 1-socket Skylake machine config-global-dhp__workload_thpfioscale XFS (no special madvise) 4 fio threads, 1 THP allocating thread -------------------------------------- 4.20-rc1 extfrag events < order 9: 1023463 4.20-rc1+patch: 358574 (65% reduction) 4.20-rc1+patch1-3: 19274 (98% reduction) 4.20-rc1+patch1-4: 1094 (99.9% reduction) 4.20.0-rc1 4.20.0-rc1 boost-v3r1 stall-v3r1 Amean fault-base-1 659.85 ( 0.00%) 658.74 ( 0.17%) Amean fault-huge-1 172.19 ( 0.00%) 168.00 ( 2.43%) thpfioscale Percentage Faults Huge 4.20.0-rc1 4.20.0-rc1 boost-v3r1 stall-v3r1 Percentage huge-1 1.68 ( 0.00%) 0.88 ( -47.52%) Fragmentation events are now reduced to negligible levels. The latencies and allocation success rates are roughly similar. Over the course of 16 minutes, there were 52 stalls due to fragmentation avoidance with a total stall time of 0.2 seconds. 1-socket Skylake machine global-dhp__workload_thpfioscale-madvhugepage-xfs (MADV_HUGEPAGE) ----------------------------------------------------------------- 4.20-rc1 extfrag events < order 9: 342549 4.20-rc1+patch: 337890 ( 1% reduction) 4.20-rc1+patch1-3: 12801 (96% reduction) 4.20-rc1+patch1-4: 1112 (99.7% reduction) 4.20.0-rc1 4.20.0-rc1 boost-v3r1 stall-v3r1 Amean fault-base-1 1578.91 ( 0.00%) 1647.00 ( -4.31%) Amean fault-huge-1 1090.23 ( 0.00%) 559.31 * 48.70%* 4.20.0-rc1 4.20.0-rc1 boost-v3r1 stall-v3r1 Percentage huge-1 82.59 ( 0.00%) 99.98 ( 21.05%) The fragmentation events were reduced and the latencies are good. This is a big difference between v2 and v3 of the series as v2 had stalls that reached the timeout of HZ/10 where as a timeout of HZ/50 has better latencies without compromising on fragmentation events or allocation success rates. There were 219 stalls over the course of 16 minutes for a total stall time of roughly 1 second (as opposed to 11 seconds with HZ/10). The distribution of stalls is as follows 209 4000 1 8000 9 20000 This shows the majority of stalls were for just one jiffie. 2-socket Haswell machine config-global-dhp__workload_thpfioscale XFS (no special madvise) 4 fio threads, 5 THP allocating threads ---------------------------------------------------------------- 4.20-rc1 extfrag events < order 9: 209820 4.20-rc1+patch: 185923 (11% reduction) 4.20-rc1+patch1-3: 11240 (95% reduction) 4.20-rc1+patch1-4: 8709 (96% reduction) 4.20.0-rc1 4.20.0-rc1 boost-v3r1 stall-v3r1 Amean fault-base-5 1395.28 ( 0.00%) 1335.23 ( 4.30%) Amean fault-huge-5 539.69 ( 0.00%) 614.88 * -13.93%* 4.20.0-rc1 4.20.0-rc1 boost-v3r1 stall-v3r1 Percentage huge-5 0.53 ( 0.00%) 2.16 ( 306.25%) There is a slight reduction in fragmentation events but it's slight enough that it may be due to luck. There is a small increase in latencies which is partially offset by a slight increase in THP allocation success rates. There were 65 stalls over the course of 63 minutes with stall time of a total of roughly 0.2 seconds. 2-socket Haswell machine global-dhp__workload_thpfioscale-madvhugepage-xfs (MADV_HUGEPAGE) ----------------------------------------------------------------- 4.20-rc1 extfrag events < order 9: 167464 4.20-rc1+patch: 130081 (22% reduction) 4.20-rc1+patch1-3: 12057 (92% reduction) 4.20-rc1+patch1-4: 11494 (93% reduction) thpfioscale Fault Latencies 4.20.0-rc1 4.20.0-rc1 boost-v3r1 stall-v3r1 Amean fault-base-5 8691.83 ( 0.00%) 7380.80 ( 15.08%) Amean fault-huge-5 2899.83 ( 0.00%) 4066.94 * -40.25%* 4.20.0-rc1 4.20.0-rc1 boost-v3r1 stall-v3r1 Percentage huge-5 95.55 ( 0.00%) 98.98 ( 3.59%) The fragmentation events are reduced and while there is some wobble on the latency, the success rate is near 100% while under heavy pressure. There were 2016 stalls over the course of 85 minutes with a total stall time of roughly 8 seconds. This patch does reduce fragmentation rates overall but it's not free as some allocataions can stall for short periods of time and there are knock-on effects to latency when THP allocation success rates are higher. While it's within acceptable limits for the adverse test case, there may be other workloads that cannot tolerate the stalls. If this occurs, it can be tuned to disable the feature or more ideally, the test case is made available for analysis to see if the stall behaviour can be reduced while still limiting the fragmentation events. On the flip-side, it has been checked that setting the fragment_stall_order to 9 eliminated fragmentation events entirely. Signed-off-by: Mel Gorman <mgorman@techsingularity.net> --- Documentation/sysctl/vm.txt | 23 +++++++++++ include/linux/mm.h | 1 + include/linux/mmzone.h | 2 + include/linux/vm_event_item.h | 1 + include/trace/events/kmem.h | 21 ++++++++++ kernel/sysctl.c | 10 +++++ mm/internal.h | 1 + mm/page_alloc.c | 93 +++++++++++++++++++++++++++++++++++++------ mm/vmstat.c | 1 + 9 files changed, 141 insertions(+), 12 deletions(-)