From: Dipankar Sarma <dipankar@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] RCU - cpu-offline-cleanup [1/3]
Date: Sat, 31 Jul 2004 14:24:03 +0530 [thread overview]
Message-ID: <20040731085402.GA4612@in.ibm.com> (raw)
Andrew,
There is a series of patches in my tree and these 3 are the first
ones that should probably be merged down the road. Descriptions are on
top of the patches. Please include them in -mm.
A lot of RCU code will be cleaned up later in order to support
call_rcu_bh(), the separate RCU interface that considers softirq
handler completion a quiescent state.
Thanks
Dipankar
Signed-off-by: Dipankar Sarma <dipankar@in.ibm.com>
Minor cleanup of the hotplug code to remove #ifdef in cpu
event notifier handler. If CONFIG_HOTPLUG_CPU is not defined,
CPU_DEAD case will be optimized off.
kernel/rcupdate.c | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff -puN kernel/rcupdate.c~cpu-offline-cleanup kernel/rcupdate.c
--- linux-2.6.8-rc2-rcu/kernel/rcupdate.c~cpu-offline-cleanup 2004-07-29 13:35:18.000000000 +0530
+++ linux-2.6.8-rc2-rcu-dipankar/kernel/rcupdate.c 2004-07-29 13:41:18.000000000 +0530
@@ -242,6 +242,12 @@ unlock:
tasklet_kill_immediate(&RCU_tasklet(cpu), cpu);
}
+#else
+
+static void rcu_offline_cpu(int cpu)
+{
+}
+
#endif
void rcu_restart_cpu(int cpu)
@@ -325,11 +331,9 @@ static int __devinit rcu_cpu_notify(stru
case CPU_UP_PREPARE:
rcu_online_cpu(cpu);
break;
-#ifdef CONFIG_HOTPLUG_CPU
case CPU_DEAD:
rcu_offline_cpu(cpu);
break;
-#endif
default:
break;
}
_
next reply other threads:[~2004-07-31 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-31 8:54 Dipankar Sarma [this message]
2004-07-31 9:01 ` [PATCH] RCU - rcu-cpu-offline-fix [2/3] Dipankar Sarma
2004-07-31 9:05 ` [PATCH] RCU - low-latency-rcu [3/3] Dipankar Sarma
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=20040731085402.GA4612@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.