public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 1/2] smp_call_function: don't use lock in call_function_data
@ 2008-08-22  0:29 Jeremy Fitzhardinge
  2008-08-22  0:36 ` Jeremy Fitzhardinge
  2008-08-22  1:47 ` Nick Piggin
  0 siblings, 2 replies; 3+ messages in thread
From: Jeremy Fitzhardinge @ 2008-08-22  0:29 UTC (permalink / raw)
  To: Ingo Molnar
  Cc: Nick Piggin, Andi Kleen, Pallipadi, Venkatesh, Suresh Siddha,
	Jens Axboe, Linux Kernel Mailing List, Rusty Russell

There's no need for a lock in call_function_data, since it's only used
to decrement-and-test a counter.  Use an atomic instead.

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
---
 kernel/smp.c |   17 ++++-------------
 1 file changed, 4 insertions(+), 13 deletions(-)

===================================================================
--- a/kernel/smp.c
+++ b/kernel/smp.c
@@ -10,6 +10,7 @@
 #include <linux/rcupdate.h>
 #include <linux/rculist.h>
 #include <linux/smp.h>
+#include <asm/atomic.h>
 
 bool __read_mostly smp_single_ipi_queue = false;
 
@@ -37,8 +38,7 @@
 
 struct call_function_data {
 	struct call_single_data csd;
-	spinlock_t lock;
-	unsigned int refs;
+	atomic_t refs;
 	cpumask_t cpumask;
 	struct rcu_head rcu_head;
 };
@@ -125,21 +125,13 @@
 	 */
 	rcu_read_lock();
 	list_for_each_entry_rcu(data, &queue->list, csd.list) {
-		int refs;
-
 		if (!cpu_isset(cpu, data->cpumask))
 			continue;
 
 		data->csd.func(data->csd.info);
 
-		spin_lock(&data->lock);
 		cpu_clear(cpu, data->cpumask);
-		WARN_ON(data->refs == 0);
-		data->refs--;
-		refs = data->refs;
-		spin_unlock(&data->lock);
-
-		if (refs)
+		if (!atomic_dec_and_test(&data->refs))
 			continue;
 
 		spin_lock(&queue->lock);
@@ -379,10 +371,9 @@
 		slowpath = 1;
 	}
 
-	spin_lock_init(&data->lock);
 	data->csd.func = func;
 	data->csd.info = info;
-	data->refs = num_cpus;
+	atomic_set(&data->refs, num_cpus);
 	data->cpumask = mask;
 
 	spin_lock_irqsave(&queue->lock, flags);



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH 1/2] smp_call_function: don't use lock in call_function_data
  2008-08-22  0:29 [PATCH 1/2] smp_call_function: don't use lock in call_function_data Jeremy Fitzhardinge
@ 2008-08-22  0:36 ` Jeremy Fitzhardinge
  2008-08-22  1:47 ` Nick Piggin
  1 sibling, 0 replies; 3+ messages in thread
From: Jeremy Fitzhardinge @ 2008-08-22  0:36 UTC (permalink / raw)
  To: Ingo Molnar
  Cc: Nick Piggin, Andi Kleen, Pallipadi, Venkatesh, Suresh Siddha,
	Jens Axboe, Linux Kernel Mailing List, Rusty Russell

Jeremy Fitzhardinge wrote:
> There's no need for a lock in call_function_data, since it's only used
> to decrement-and-test a counter.  Use an atomic instead.

BTW, these two patches are against tip.git.

    J

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH 1/2] smp_call_function: don't use lock in call_function_data
  2008-08-22  0:29 [PATCH 1/2] smp_call_function: don't use lock in call_function_data Jeremy Fitzhardinge
  2008-08-22  0:36 ` Jeremy Fitzhardinge
@ 2008-08-22  1:47 ` Nick Piggin
  1 sibling, 0 replies; 3+ messages in thread
From: Nick Piggin @ 2008-08-22  1:47 UTC (permalink / raw)
  To: Jeremy Fitzhardinge
  Cc: Ingo Molnar, Andi Kleen, Pallipadi, Venkatesh, Suresh Siddha,
	Jens Axboe, Linux Kernel Mailing List, Rusty Russell

On Friday 22 August 2008 10:29, Jeremy Fitzhardinge wrote:
> There's no need for a lock in call_function_data, since it's only used
> to decrement-and-test a counter.  Use an atomic instead.

Actually I wanted to convert the cpu_clear operation to be non-atomic,
and keep it under the lock. Thus the spinlock would save one atomic
operation. I simply forgot about this after Jens took over the patchset.

We could get rid of that WARN_ON branch in 2.6.28 I expect, unless we
see it trigger.

>
> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> ---
>  kernel/smp.c |   17 ++++-------------
>  1 file changed, 4 insertions(+), 13 deletions(-)
>
> ===================================================================
> --- a/kernel/smp.c
> +++ b/kernel/smp.c
> @@ -10,6 +10,7 @@
>  #include <linux/rcupdate.h>
>  #include <linux/rculist.h>
>  #include <linux/smp.h>
> +#include <asm/atomic.h>
>
>  bool __read_mostly smp_single_ipi_queue = false;
>
> @@ -37,8 +38,7 @@
>
>  struct call_function_data {
>  	struct call_single_data csd;
> -	spinlock_t lock;
> -	unsigned int refs;
> +	atomic_t refs;
>  	cpumask_t cpumask;
>  	struct rcu_head rcu_head;
>  };
> @@ -125,21 +125,13 @@
>  	 */
>  	rcu_read_lock();
>  	list_for_each_entry_rcu(data, &queue->list, csd.list) {
> -		int refs;
> -
>  		if (!cpu_isset(cpu, data->cpumask))
>  			continue;
>
>  		data->csd.func(data->csd.info);
>
> -		spin_lock(&data->lock);
>  		cpu_clear(cpu, data->cpumask);
> -		WARN_ON(data->refs == 0);
> -		data->refs--;
> -		refs = data->refs;
> -		spin_unlock(&data->lock);
> -
> -		if (refs)
> +		if (!atomic_dec_and_test(&data->refs))
>  			continue;
>
>  		spin_lock(&queue->lock);
> @@ -379,10 +371,9 @@
>  		slowpath = 1;
>  	}
>
> -	spin_lock_init(&data->lock);
>  	data->csd.func = func;
>  	data->csd.info = info;
> -	data->refs = num_cpus;
> +	atomic_set(&data->refs, num_cpus);
>  	data->cpumask = mask;
>
>  	spin_lock_irqsave(&queue->lock, flags);

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-08-22  1:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-22  0:29 [PATCH 1/2] smp_call_function: don't use lock in call_function_data Jeremy Fitzhardinge
2008-08-22  0:36 ` Jeremy Fitzhardinge
2008-08-22  1:47 ` Nick Piggin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox