From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Manfred Spraul <manfred@colorfullife.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH -mm 0/6] rcu: introduce kfree_rcu V2
Date: Tue, 03 Mar 2009 21:44:13 +0800 [thread overview]
Message-ID: <49AD342D.6030609@cn.fujitsu.com> (raw)
There are 23 instances where the rcu callback just does
kfree(containerof(head,struct whatever_struct,rcu_member));
The 23 instances exist because there are 23 'struct whatever_struct' with
their individual rcu_member. These patches creates a generic kfree_rcu()
function that removes the need for these 23 helpers.
The number of this kind of rcu callback will increase, for this is the
most common way to use rcu and define rcu callback.
And kfree_rcu() is also help for unloadable modules, kfree_rcu() does not
queue any function which belong to the module, so a rcu_barrier() can
be avoid when module exit. (If we queue any other function by call_rcu(),
rcu_barrier() is still needed.)
Changed from V1:
1) Implement kfree_rcu() in slab layer.
In V1, the offset from the container struct to the rcu member
is calculated at compile time and stored in head->func instead of the
function pointer. This disarrange rcu's algorithm a little, there is
no bad side effect when we implement kfree_rcu() in slab layer.
2) kfree_rcu() API is changed, use the version that Manfred Spraul designed.
This one allows compiler do more checking.
Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
---
next reply other threads:[~2009-03-03 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 13:44 Lai Jiangshan [this message]
2009-03-03 14:09 ` [PATCH -mm 0/6] rcu: introduce kfree_rcu V2 Ingo Molnar
2009-03-04 9:22 ` Lai Jiangshan
2009-03-04 11:45 ` Ingo Molnar
2009-03-04 12:00 ` Pekka Enberg
2009-03-06 10:23 ` [PATCH] rcu: introduce kfree_rcu V3 Lai Jiangshan
2009-03-07 5:31 ` Paul E. McKenney
2009-03-03 15:11 ` [PATCH -mm 0/6] rcu: introduce kfree_rcu V2 Nick Piggin
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=49AD342D.6030609@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).