mm/slub: Fix count_partial() problem
v4 cover mm/slub: Fix count_partial() problem
count_partial() can hold n->list_lock spinlock for quite long, which makes much trouble to the system. This series eliminate this problem.
v1->v2:
- Improved changelog and variable naming for PATCH 1~2.
- PATCH3 adds per-cpu counter to avoid performance regression in concurrent __slab_free().
v2->v3:
- Changed "page->inuse" to the safe "new.inuse", etc.
- Used CONFIG_SLUB_DEBUG and CONFIG_SYSFS condition for new counters.
- atomic_long_t -> unsigned long
v3->v4:
- introduced new CONFIG_SLUB_DEBUG_PARTIAL to give a chance to be enabled for production use.
- Merged PATCH 4 into PATCH 1.
[Testing]
There seems might be a little performance impact under extreme __slab_free() concurrent calls according to my tests.
On my 32-cpu 2-socket physical machine:
Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
1) perf stat --null --repeat 10 -- hackbench 20 thread 20000
== original, no patched
Performance counter stats for 'hackbench 20 thread 20000' (10 runs):
24.536050899 seconds time elapsed ( +- 0.24% )
Performance counter stats for 'hackbench 20 thread 20000' (10 runs):
24.588049142 seconds time elapsed ( +- 0.35% )
== patched with patch1~4
Performance counter stats for 'hackbench 20 thread 20000' (10 runs):
24.670892273 seconds time elapsed ( +- 0.29% )
Performance counter stats for 'hackbench 20 thread 20000' (10 runs):
24.746755689 seconds time elapsed ( +- 0.21% )
2) perf stat --null --repeat 10 -- hackbench 32 thread 20000
== original, no patched
Performance counter stats for 'hackbench 32 thread 20000' (10 runs):
39.784911855 seconds time elapsed ( +- 0.14% )
Performance counter stats for 'hackbench 32 thread 20000' (10 runs):
39.868687608 seconds time elapsed ( +- 0.19% )
== patched with patch1~4
Performance counter stats for 'hackbench 32 thread 20000' (10 runs):
39.681273015 seconds time elapsed ( +- 0.21% )
Performance counter stats for 'hackbench 32 thread 20000' (10 runs):
39.681238459 seconds time elapsed ( +- 0.09% )
Xunlei Pang (3):
mm/slub: Introduce two counters for partial objects
percpu: Export per_cpu_sum()
mm/slub: Get rid of count_partial()
include/linux/percpu-defs.h | 10 ++++ init/Kconfig | 13 +++++ kernel/locking/percpu-rwsem.c | 10 ---- mm/slab.h | 6 ++ mm/slub.c | 129 +++++++++++++++++++++++++++++------------- 5 files changed, 120 insertions(+), 48 deletions(-)
Signature · 1 line
1.8.3.1
PATCH v4 1/3 mm/slub: Introduce two counters for partial objects
The node list_lock in count_partial() spends long time iterating in case of large amount of partial page lists, which can cause thunder herd effect to the list_lock contention.
We have HSF RT(High-speed Service Framework Response-Time) monitors, the RT figures fluctuated randomly, then we deployed a tool detecting "irq off" and "preempt off" to dump the culprit's calltrace, capturing the list_lock cost nearly 100ms with irq off issued by "ss", this also caused network timeouts.
This patch introduces two counters to maintain the actual number of partial objects dynamically instead of iterating the partial page lists with list_lock held.
New counters of kmem_cache_node: partial_free_objs, partial_total_objs. The main operations are under list_lock in slow path, its performance impact is expected to be minimal except the __slab_free() path.
The only concern of introducing partial counter is that partial_free_objs may cause cacheline contention and false sharing issues in case of same SLUB concurrent __slab_free(), so define it to be a percpu counter and places it carefully.
As "Vlastimil Babka" and "Christoph Lameter" both suggested that we don't care about the accurate partial objects, and in case that somebody might actually want accurate object statistics at the expense of peak performance, and it would be nice to give them such option in SLUB.
Thus a new CONFIG_SLUB_DEBUG_PARTIAL is introduced to maintain accurate partial objects, which is default off to avoid unexpected performance degradation.
When CONFIG_SLUB_DEBUG_PARTIAL is not selected, the sysfs or proc files related to the partial list (/proc/slabinfo, sysfs objects_partial, etc) assume their zero usage data, e.g.,
Value of "active_objs" and "num_objs" fields of "/proc/slabinfo" equal. "cat /sys/kernel/slab/<slab>/partial" displays "0".
--- init/Kconfig | 13 +++++++++++++ mm/slab.h | 6 ++++++ mm/slub.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++---- 3 files changed, 78 insertions(+), 4 deletions(-)
init/Kconfig +13 -0
@@ -1867,6 +1867,19 @@ config SLUB_DEBUG SLUB sysfs support. /sys/slab will not exist and there will be no support for cache validation etc. +config SLUB_DEBUG_PARTIAL + default n + bool "Enable SLUB debugging for the node partial list" if EXPERT + depends on SLUB && SYSFS + help + Maintain runtime counters for the node partial list debugging. + When CONFIG_SLUB_DEBUG_PARTIAL is not selected, the sysfs or proc + files related to the partial list assume zero data usage, e.g., + value of "active_objs" and "num_objs" of "/proc/slabinfo" equals. + "cat /sys/kernel/slab/<slab>/partial" displays "0". + + It might have slight performance impact for production use. + config COMPAT_BRK bool "Disable heap randomization" default y
mm/slab.h +6 -0
@@ -546,12 +546,18 @@ struct kmem_cache_node {#ifdef CONFIG_SLUB unsigned long nr_partial; +#ifdef CONFIG_SLUB_DEBUG_PARTIAL +unsigned long partial_total_objs; +#endif struct list_head partial;#ifdef CONFIG_SLUB_DEBUG atomic_long_t nr_slabs;atomic_long_t total_objects;struct list_head full;#endif +#ifdef CONFIG_SLUB_DEBUG_PARTIAL +unsigned long __percpu *partial_free_objs____cacheline_aligned_in_smp ; +#endif #endif };
mm/slub.c +59 -4
168 lines not on this page · raw message
Signature · 1 line
1.8.3.1
Re: [PATCH v4 1/3] mm/slub: Introduce two counters for partial objects
Quoted 14 lines · Xunlei Pang
The node
list_lockincount_partial()spends long time iterating in case of large amount of partial page lists, which can cause thunder herd effect to thelist_lockcontention.We have HSF RT(High-speed Service Framework Response-Time) monitors, the RT figures fluctuated randomly, then we deployed a tool detecting "irq off" and "preempt off" to dump the culprit's calltrace, capturing the
list_lockcost nearly 100ms with irq off issued by "ss", this also caused network timeouts.This patch introduces two counters to maintain the actual number of partial objects dynamically instead of iterating the partial page lists with
list_lockheld.
Quoted 8 lines
New counters of
kmem_cache_node:partial_free_objs,partial_total_objs. The main operations are underlist_lockin slow path, its performance impact is expected to be minimal except the__slab_free()path.The only concern of introducing partial counter is that
partial_free_objsmay cause cacheline contention and false sharing issues in case of same SLUB concurrent__slab_free(), so define it to be a percpu counter and places it carefully.
Hm I wonder, is it possible that this will eventually overflow/underflow the counter on some CPU? (I guess practially only on 32bit). Maybe the operations that are already done under n->list_lock should flush the percpu counter to a shared counter?
...
mm/slub.c static void __slab_free(struct kmem_cache *s, struct page *page, · line 3074
Quoted 10 lines
mm/slub.c +6
-0@@ -3039,6 +3066,13 @@ static void __slab_free(struct kmem_cache *s, struct page *page, head, new.counters, "__slab_free")); +if (!was_frozen && prior) { +if (n) +__update_partial_free (n, cnt); +else +__update_partial_free (get_node (s,page_to_nid (page)), cnt); + }
I would guess this is the part that makes your measurements notice that (although tiny) difference. We didn't need to obtain the node pointer before and now we do. And that is really done just for the per-node breakdown in "objects" and "objects_partial" files under /sys/kernel/slab - distinguishing nodes is not needed for /proc/slabinfo. So that kinda justifies putting this under a new CONFIG as you did. Although perhaps somebody interested in these kind of stats would enable CONFIG_SLUB_STATS anyway, so that's still an option to use instead of introducing a new oddly specific CONFIG? At least until somebody comes up and presents an use case where they want the per-node breakdowns in /sys but cannot afford CONFIG_SLUB_STATS.
But I'm also still thinking about simply counting all free objects (for the purposes of accurate <active_objs> in /proc/slabinfo) as a percpu variable in struct kmem_cache itself. That would basically put this_cpu_add() in all the fast paths, but AFAICS thanks to the segment register it doesn't mean disabling interrupts nor a LOCK operation, so maybe it wouldn't be that bad? And it shouldn't need to deal with these node pointers. So maybe that would be acceptable for CONFIG_SLUB_DEBUG? Guess I'll have to try...
Re: [PATCH v4 1/3] mm/slub: Introduce two counters for partial objects
Quoted 24 lines · Vlastimil Babka
Quoted 14 lines · Xunlei Pang
The node
list_lockincount_partial()spends long time iterating in case of large amount of partial page lists, which can cause thunder herd effect to thelist_lockcontention.We have HSF RT(High-speed Service Framework Response-Time) monitors, the RT figures fluctuated randomly, then we deployed a tool detecting "irq off" and "preempt off" to dump the culprit's calltrace, capturing the
list_lockcost nearly 100ms with irq off issued by "ss", this also caused network timeouts.This patch introduces two counters to maintain the actual number of partial objects dynamically instead of iterating the partial page lists with
list_lockheld.Quoted 8 lines
New counters of
kmem_cache_node:partial_free_objs,partial_total_objs. The main operations are underlist_lockin slow path, its performance impact is expected to be minimal except the__slab_free()path.The only concern of introducing partial counter is that
partial_free_objsmay cause cacheline contention and false sharing issues in case of same SLUB concurrent__slab_free(), so define it to be a percpu counter and places it carefully.
Quoted 4 lines
Hm I wonder, is it possible that this will eventually overflow/underflow the counter on some CPU? (I guess practially only on 32bit). Maybe the operations that are already done under
n->list_lockshould flush the percpu counter to a shared counter?
You are right, thanks a lot for noticing this.
Quoted 25 lines
...
mm/slub.c static void __slab_free(struct kmem_cache *s, struct page *page, · line 3074
Quoted 10 lines
mm/slub.c +6
-0@@ -3039,6 +3066,13 @@ static void __slab_free(struct kmem_cache *s, struct page *page, head, new.counters, "__slab_free")); +if (!was_frozen && prior) { +if (n) +__update_partial_free (n, cnt); +else +__update_partial_free (get_node (s,page_to_nid (page)), cnt); + }I would guess this is the part that makes your measurements notice that (although tiny) difference. We didn't need to obtain the node pointer before and now we do. And that is really done just for the per-node breakdown in "objects" and "
objects_partial" files under/sys/kernel/slab- distinguishing nodes is not needed for/proc/slabinfo. So that kinda justifies putting this under a new CONFIG as you did. Although perhaps somebody interested in these kind of stats would enableCONFIG_SLUB_STATSanyway, so that's still an option to use instead of introducing a new oddly specific CONFIG? At least until somebody comes up and presents an use case where they want the per-node breakdowns in /sys but cannot affordCONFIG_SLUB_STATS.
Quoted 8 lines
But I'm also still thinking about simply counting all free objects (for the purposes of accurate <
active_objs> in/proc/slabinfo) as a percpu variable in structkmem_cacheitself. That would basically putthis_cpu_add()in all the fast paths, but AFAICS thanks to the segment register it doesn't mean disabling interrupts nor a LOCK operation, so maybe it wouldn't be that bad? And it shouldn't need to deal with these node pointers. So maybe that would be acceptable forCONFIG_SLUB_DEBUG? Guess I'll have to try...
The percpu operation itself should be fine, it looks to be cacheline pingpong issue due to extra percpu counter access, so making it cacheline aligned improves a little according to my tests.
Re: [PATCH v4 1/3] mm/slub: Introduce two counters for partial objects
In reply to Xunlei PangQuoted 9 lines · Xunlei Pang
The node
list_lockincount_partial()spends long time iterating in case of large amount of partial page lists, which can cause thunder herd effect to thelist_lockcontention.We have HSF RT(High-speed Service Framework Response-Time) monitors, the RT figures fluctuated randomly, then we deployed a tool detecting "irq off" and "preempt off" to dump the culprit's calltrace, capturing the
list_lockcost nearly 100ms with irq off issued by "ss", this also caused network timeouts.
I forgot to ask, how does "ss" come into this? It displays network connections AFAIK. Does it read any SLUB counters or slabinfo?
Re: [PATCH v4 1/3] mm/slub: Introduce two counters for partial objects
Quoted 5 lines · Vlastimil Babka
Quoted 4 lines · Xunlei Pang
The node
list_lockincount_partial()spends long time iterating in case of large amount of partial page lists, which can cause thunder herd effect to thelist_lockcontention.
Quoted 9 lines
Quoted 5 lines
We have HSF RT(High-speed Service Framework Response-Time) monitors, the RT figures fluctuated randomly, then we deployed a tool detecting "irq off" and "preempt off" to dump the culprit's calltrace, capturing the
list_lockcost nearly 100ms with irq off issued by "ss", this also caused network timeouts.I forgot to ask, how does "ss" come into this? It displays network connections AFAIK. Does it read any SLUB counters or slabinfo?
ss may access /proc/slabinfo to acquire network related slab statistics.
Re: [PATCH v4 1/3] mm/slub: Introduce two counters for partial objects
More precisely, ss will count partial objects like denty objects with
"/sys/kernel/slab/dentry/partial" whose number can become huge.
Quoted 20 lines · Xunlei Pang
Quoted 5 lines · Vlastimil Babka
Quoted 4 lines · Xunlei Pang
The node
list_lockincount_partial()spends long time iterating in case of large amount of partial page lists, which can cause thunder herd effect to thelist_lockcontention.Quoted 9 lines
Quoted 5 lines
We have HSF RT(High-speed Service Framework Response-Time) monitors, the RT figures fluctuated randomly, then we deployed a tool detecting "irq off" and "preempt off" to dump the culprit's calltrace, capturing the
list_lockcost nearly 100ms with irq off issued by "ss", this also caused network timeouts.I forgot to ask, how does "ss" come into this? It displays network connections AFAIK. Does it read any SLUB counters or slabinfo?
ss may access
/proc/slabinfoto acquire network related slab statistics.
Re: [PATCH v4 1/3] mm/slub: Introduce two counters for partial objects
Quoted 2 lines · Shu Ming
More precisely, ss will count partial objects like denty objects with
"/sys/kernel/slab/dentry/partial" whose number can become huge.
Uh, that's interesting. Would you know what exactly it uses the value for? I can think of several reasons why it might be misleading.
Quoted 22 lines · Xunlei Pang
Quoted 20 lines · Vlastimil Babka
Quoted 5 lines · Xunlei Pang
Quoted 4 lines
The node
list_lockincount_partial()spends long time iterating in case of large amount of partial page lists, which can cause thunder herd effect to thelist_lockcontention.Quoted 9 lines
Quoted 5 lines
We have HSF RT(High-speed Service Framework Response-Time) monitors, the RT figures fluctuated randomly, then we deployed a tool detecting "irq off" and "preempt off" to dump the culprit's calltrace, capturing the
list_lockcost nearly 100ms with irq off issued by "ss", this also caused network timeouts.I forgot to ask, how does "ss" come into this? It displays network connections AFAIK. Does it read any SLUB counters or slabinfo?
ss may access
/proc/slabinfoto acquire network related slab statistics.
Re: [PATCH v4 1/3] mm/slub: Introduce two counters for partial objects
I am not sure how people are using partial object accounting. I believe it is used as a memory usage hint of slabs.
Quoted 31 lines · Vlastimil Babka
Quoted 2 lines · Shu Ming
More precisely, ss will count partial objects like denty objects with
"/sys/kernel/slab/dentry/partial" whose number can become huge.Uh, that's interesting. Would you know what exactly it uses the value for? I can think of several reasons why it might be misleading.
Quoted 22 lines · Xunlei Pang
Quoted 20 lines · Vlastimil Babka
Quoted 5 lines · Xunlei Pang
Quoted 4 lines
The node
list_lockincount_partial()spends long time iterating in case of large amount of partial page lists, which can cause thunder herd effect to thelist_lockcontention.Quoted 9 lines
Quoted 5 lines
We have HSF RT(High-speed Service Framework Response-Time) monitors, the RT figures fluctuated randomly, then we deployed a tool detecting "irq off" and "preempt off" to dump the culprit's calltrace, capturing the
list_lockcost nearly 100ms with irq off issued by "ss", this also caused network timeouts.I forgot to ask, how does "ss" come into this? It displays network connections AFAIK. Does it read any SLUB counters or slabinfo?
ss may access
/proc/slabinfoto acquire network related slab statistics.
PATCH v4 2/3 percpu: Export per_cpu_sum()
In reply to Xunlei Pangper_cpu_sum() is useful, and deserves to be exported.
--- include/linux/percpu-defs.h | 10 ++++++++++ kernel/locking/percpu-rwsem.c | 10 ---------- 2 files changed, 10 insertions(+), 10 deletions(-)
include/linux/percpu-defs.h +10 -0
@@ -220,6 +220,16 @@ (void )__vpp_verify; \ } while (0) +#define per_cpu_sum (var) \ +({ \ + typeof(var) __sum = 0; \ + int cpu; \ + compiletime_assert_atomic_type(__sum); \ + for_each_possible_cpu(cpu) \ + __sum += per_cpu(var, cpu); \ + __sum; \ +}) +#ifdef CONFIG_SMP /*
kernel/locking/percpu-rwsem.c +0 -10
@@ -178,16 +178,6 @@ bool __percpu_down_read(struct percpu_rw_semaphore *sem, bool try) }EXPORT_SYMBOL_GPL (__percpu_down_read); -#define per_cpu_sum (var) \ -({ \ - typeof(var) __sum = 0; \ - int cpu; \ - compiletime_assert_atomic_type(__sum); \ - for_each_possible_cpu(cpu) \ - __sum += per_cpu(var, cpu); \ - __sum; \ -}) -/* * Return true if the modular sum of the sem->read_count per-CPU variable is * zero. If this sum is zero, then it is stable due to the fact that if any
Signature · 1 line
1.8.3.1
PATCH v4 3/3 mm/slub: Get rid of count_partial()
In reply to Xunlei PangNow the partial counters are ready, let's use them to get rid of count_partial().
The partial counters will involve in to calculate the accurate partial usage when CONFIG_SLUB_DEBUG_PARTIAL is on, otherwise simply assume their zero usage statistics.
--- mm/slub.c | 64 +++++++++++++++++++++++++++++++-------------------------------- 1 file changed, 31 insertions(+), 33 deletions(-)
mm/slub.c +31 -33
@@ -2533,11 +2533,6 @@ static inline int node_match(struct page *page, int node) }#ifdef CONFIG_SLUB_DEBUG -static int count_free (struct page *page) -{ -return page->objects - page->inuse; -} -static inline unsigned long node_nr_objs (struct kmem_cache_node *n) {return atomic_long_read (&n->total_objects);
@@ -2545,18 +2540,33 @@ static inline unsigned long node_nr_objs(struct kmem_cache_node *n)#endif /* CONFIG_SLUB_DEBUG */ #if defined(CONFIG_SLUB_DEBUG ) || defined(CONFIG_SYSFS ) -static unsigned long count_partial (struct kmem_cache_node *n, -int (*get_count)(struct page *)) +enum partial_item {PARTIAL_FREE ,PARTIAL_INUSE ,PARTIAL_TOTAL ,PARTIAL_SLAB }; + +static unsigned long partial_counter (struct kmem_cache_node *n, +enum partial_item item) { -unsigned long flags; -unsigned long x =0 ; -struct page *page; +unsigned long ret =0 ; -spin_lock_irqsave (&n->list_lock, flags); -list_for_each_entry (page, &n->partial, slab_list) - x +=get_count (page); -spin_unlock_irqrestore (&n->list_lock, flags); -return x; +#ifdef CONFIG_SLUB_DEBUG_PARTIAL +if (item ==PARTIAL_FREE ) { + ret =per_cpu_sum (*n->partial_free_objs); +if ((long )ret <0 ) + ret =0 ; + }else if (item ==PARTIAL_TOTAL ) { + ret = n->partial_total_objs; + }else if (item ==PARTIAL_INUSE ) { + ret =per_cpu_sum (*n->partial_free_objs); +if ((long )ret <0 ) + ret =0 ; + ret = n->partial_total_objs - ret; +if ((long )ret <0 ) + ret =0 ; + }else {/* item == PARTIAL_SLAB */ + ret = n->nr_partial; + } +#endif + +return ret; }#endif /* CONFIG_SLUB_DEBUG || CONFIG_SYSFS */
@@ -2587,7 +2597,7 @@ static unsigned long count_partial(struct kmem_cache_node *n,unsigned long nr_objs;unsigned long nr_free; - nr_free =count_partial (n, count_free); + nr_free =partial_counter (n,PARTIAL_FREE ); nr_slabs =node_nr_slabs (n); nr_objs =node_nr_objs (n);
@@ -4654,18 +4664,6 @@ void *__kmalloc_node_track_caller(size_t size, gfp_t gfpflags,EXPORT_SYMBOL (__kmalloc_node_track_caller);#endif -#ifdef CONFIG_SYSFS -static int count_inuse (struct page *page) -{ -return page->inuse; -} - -static int count_total (struct page *page) -{ -return page->objects; -} -#endif -#ifdef CONFIG_SLUB_DEBUG static void validate_slab (struct kmem_cache *s,struct page *page) {
@@ -5102,7 +5100,7 @@ static ssize_t show_slab_objects(struct kmem_cache *s, x =atomic_long_read (&n->total_objects); else if (flags & SO_OBJECTS) x =atomic_long_read (&n->total_objects) - -count_partial (n, count_free); +partial_counter (n,PARTIAL_FREE ); else x =atomic_long_read (&n->nr_slabs); total += x;
@@ -5116,11 +5114,11 @@ static ssize_t show_slab_objects(struct kmem_cache *s,for_each_kmem_cache_node (s, node, n) {if (flags &SO_TOTAL ) - x =count_partial (n, count_total); + x =partial_counter (n,PARTIAL_TOTAL );else if (flags &SO_OBJECTS ) - x =count_partial (n, count_inuse); + x =partial_counter (n,PARTIAL_INUSE );else - x = n->nr_partial; + x =partial_counter (n,PARTIAL_SLAB ); total += x; nodes[node] += x; }
@@ -5884,7 +5882,7 @@ void get_slabinfo(struct kmem_cache *s, struct slabinfo *sinfo)for_each_kmem_cache_node (s, node, n) { nr_slabs +=node_nr_slabs (n); nr_objs +=node_nr_objs (n); - nr_free +=count_partial (n, count_free); + nr_free +=partial_counter (n,PARTIAL_FREE ); } sinfo->active_objs = nr_objs - nr_free;
Signature · 1 line
1.8.3.1