Subject: [PATCH 14/16] slub: only IPI CPUs that have per cpu obj to flush
From: Sebastian Andrzej Siewior <[email-masked]>
To: Steven Rostedt <[email-masked]>
Cc: [email-masked], [email-masked], Carsten Emde <[email-masked]>, Gilad Ben-Yossef <[email-masked]>, Chris Metcalf <[email-masked]>, Frederic Weisbecker <[email-masked]>, Russell King <[email-masked]>, Pekka Enberg <[email-masked]>, Matt Mackall <[email-masked]>, Sasha Levin <[email-masked]>, Rik van Riel <[email-masked]>, Andi Kleen <[email-masked]>, Mel Gorman <[email-masked]>, Alexander Viro <[email-masked]>, Avi Kivity <[email-masked]>, Michal Nazarewicz <[email-masked]>, Kosaki Motohiro <
Date: Wed, 13 Feb 2013 17:12:09 +0100
List-Id: <linux-rt-users.vger.kernel.org>

From: Gilad Ben-Yossef <[email-masked]>

flush_all() is called for each kmem_cache_destroy().  So every cache being
destroyed dynamically ends up sending an IPI to each CPU in the system,
regardless if the cache has ever been used there.

For example, if you close the Infinband ipath driver char device file, the
close file ops calls kmem_cache_destroy().  So running some infiniband
config tool on one a single CPU dedicated to system tasks might interrupt
the rest of the 127 CPUs dedicated to some CPU intensive or latency
sensitive task.

I suspect there is a good chance that every line in the output of "git
grep kmem_cache_destroy linux/ | grep '\->'" has a similar scenario.

This patch attempts to rectify this issue by sending an IPI to flush the
per cpu objects back to the free lists only to CPUs that seem to have such
objects.

The check which CPU to IPI is racy but we don't care since asking a CPU
without per cpu objects to flush does no damage and as far as I can tell
the flush_all by itself is racy against allocs on remote CPUs anyway, so
if you required the flush_all to be determinstic, you had to arrange for
locking regardless.

Without this patch the following artificial test case:

$ cd /sys/kernel/slab
$ for DIR in *; do cat $DIR/alloc_calls > /dev/null; done

produces 166 IPIs on an cpuset isolated CPU. With it it produces none.

The code path of memory allocation failure for CPUMASK_OFFSTACK=y
config was tested using fault injection framework.

Signed-off-by: Gilad Ben-Yossef <[email-masked]>
Acked-by: Christoph Lameter <[email-masked]>
Cc: Chris Metcalf <[email-masked]>
Acked-by: Peter Zijlstra <[email-masked]>
Cc: Frederic Weisbecker <[email-masked]>
Cc: Russell King <[email-masked]>
Cc: Pekka Enberg <[email-masked]>
Cc: Matt Mackall <[email-masked]>
Cc: Sasha Levin <[email-masked]>
Cc: Rik van Riel <[email-masked]>
Cc: Andi Kleen <[email-masked]>
Cc: Mel Gorman <[email-masked]>
Cc: Alexander Viro <[email-masked]>
Cc: Avi Kivity <[email-masked]>
Cc: Michal Nazarewicz <[email-masked]>
Cc: Kosaki Motohiro <[email-masked]>
Cc: Milton Miller <[email-masked]>
Signed-off-by: Andrew Morton <[email-masked]>
Signed-off-by: Linus Torvalds <[email-masked]>
Signed-off-by: Sebastian Andrzej Siewior <[email-masked]>
---
 mm/slub.c |   10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

Index: linux-3.2.35-rt53/mm/slub.c
===================================================================
--- linux-3.2.35-rt53.orig/mm/slub.c
+++ linux-3.2.35-rt53/mm/slub.c
@@ -2030,9 +2030,17 @@ static void flush_cpu_slab(void *d)
 	__flush_cpu_slab(s, smp_processor_id());
 }
 
+static bool has_cpu_slab(int cpu, void *info)
+{
+	struct kmem_cache *s = info;
+	struct kmem_cache_cpu *c = per_cpu_ptr(s->cpu_slab, cpu);
+
+	return !!(c->page);
+}
+
 static void flush_all(struct kmem_cache *s)
 {
-	on_each_cpu(flush_cpu_slab, s, 1);
+	on_each_cpu_cond(has_cpu_slab, flush_cpu_slab, s, 1, GFP_ATOMIC);
 }
 
 /*