public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gautham R Shenoy <ego@in.ibm.com>
To: akpm@osdl.org, vatsa@in.ibm.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, torvalds@osdl.org,
	dipankar@in.ibm.com
Subject: [PATCH] Handle per-subsystem mutexes for CONFIG_HOTPLUG_CPU not set.
Date: Thu, 23 Nov 2006 18:48:52 +0530	[thread overview]
Message-ID: <20061123131852.GA20313@in.ibm.com> (raw)

When CONFIG_HOTPLUG_CPU is not set, lock_cpu_hotplug() and 
unlock_cpu_hotplug() default to no-ops.

However, in case of the proposed per-subsystem hotcpu mutex scheme, 
the hotcpu mutexes will be taken/released, even when
CONFIG_HOTPLUG_CPU is not set. This is an unnecessary overhead
both w.r.t space and time ;-)

This patch

* Provides a common interface for all the subsystems to lock and
unlock their per-subsystem hotcpu mutexes.
When CONFIG_HOTPLUG_CPU is not set, these operations would be no-ops.

Usage:
a) Each hotcpu aware subsystem defines the hotcpu_mutex as follows
#ifdef CONFIG_HOTPLUG_CPU
DEFINE_MUTEX(my_hotcpu_mutex);
#endif

b) The hotcpu aware subsystem uses
cpuhotplug_mutex_lock(&my_hotcpu_mutex)
and 
cpuhotplug_mutex_unlock(&my_hotcpu_mutex) 
instead of the usual mutex_lock/mutex_unlock.

Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>

---
 include/linux/cpu.h |   15 +++++++++++++++
 1 files changed, 15 insertions(+)

Index: hotplug/include/linux/cpu.h
===================================================================
--- hotplug.orig/include/linux/cpu.h
+++ hotplug/include/linux/cpu.h
@@ -24,6 +24,7 @@
 #include <linux/compiler.h>
 #include <linux/cpumask.h>
 #include <asm/semaphore.h>
+#include <linux/mutex.h>
 
 struct cpu {
 	int node_id;		/* The node which contains the CPU */
@@ -74,6 +75,17 @@ extern struct sysdev_class cpu_sysdev_cl
 
 #ifdef CONFIG_HOTPLUG_CPU
 /* Stop CPUs going up and down. */
+
+static inline void cpuhotplug_mutex_lock(struct mutex *cpu_hp_mutex)
+{
+	mutex_lock(cpu_hp_mutex);
+}
+
+static inline void cpuhotplug_mutex_unlock(struct mutex *cpu_hp_mutex)
+{
+	mutex_unlock(cpu_hp_mutex);
+}
+
 extern void lock_cpu_hotplug(void);
 extern void unlock_cpu_hotplug(void);
 #define hotcpu_notifier(fn, pri) {				\
@@ -86,6 +98,9 @@ extern void unlock_cpu_hotplug(void);
 int cpu_down(unsigned int cpu);
 #define cpu_is_offline(cpu) unlikely(!cpu_online(cpu))
 #else
+#define cpuhotplug_mutex_lock(m)	do { } while (0)
+#define cpuhotplug_mutex_unlock(m)	do { } while (0)
+
 #define lock_cpu_hotplug()	do { } while (0)
 #define unlock_cpu_hotplug()	do { } while (0)
 #define lock_cpu_hotplug_interruptible() 0
-- 
Gautham R Shenoy
Linux Technology Center
IBM India.
"Freedom comes with a price tag of responsibility, which is still a bargain,
because Freedom is priceless!"

             reply	other threads:[~2006-11-23 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23 13:18 Gautham R Shenoy [this message]
2006-11-23 20:54 ` [PATCH] Handle per-subsystem mutexes for CONFIG_HOTPLUG_CPU not set Andrew Morton
2006-11-24  4:27   ` Gautham R Shenoy
2006-11-24 12:13     ` [PATCH][v2] " Gautham R Shenoy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061123131852.GA20313@in.ibm.com \
    --to=ego@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@osdl.org \
    --cc=vatsa@in.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox