From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nick Piggin <npiggin@suse.de>, Jens Axboe <jens.axboe@oracle.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: [PATCH 2.5/2] generic-smp: remove cfd rcu_head
Date: Sat, 14 Feb 2009 15:46:47 +0100 [thread overview]
Message-ID: <1234622807.4698.32.camel@laptop> (raw)
In-Reply-To: <20090212223750.384627915@chello.nl>
Subject: generic-smp: remove cfd rcu_head
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
Date: Sat Feb 14 15:41:24 CET 2009
Since we no longer use call_rcu() on call_function_data, we can remove the
rcu_head structure from it.
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
kernel/smp.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
Index: linux-2.6/kernel/smp.c
===================================================================
--- linux-2.6.orig/kernel/smp.c
+++ linux-2.6/kernel/smp.c
@@ -39,10 +39,7 @@ struct call_function_data {
struct call_single_data csd;
spinlock_t lock;
unsigned int refs;
- union {
- struct rcu_head rcu_head;
- unsigned int stamp;
- };
+ unsigned int stamp;
struct cpumask cpumask;
};
prev parent reply other threads:[~2009-02-14 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 22:32 [PATCH 0/2] generic smp helpers vs kmalloc Peter Zijlstra
2009-02-12 22:32 ` [PATCH 1/2] generic-smp: remove single ipi fallback for smp_call_function_many() Peter Zijlstra
2009-02-14 14:41 ` [PATCH 1.5/2] generic-smp: fix initial quiesent count Peter Zijlstra
2009-02-14 14:46 ` Peter Zijlstra
2009-02-14 21:14 ` Peter Zijlstra
2009-02-14 23:29 ` Ingo Molnar
2009-02-12 22:32 ` [PATCH 2/2] generic-smp: remove kmalloc usage Peter Zijlstra
2009-02-14 14:46 ` Peter Zijlstra [this message]
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=1234622807.4698.32.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox