From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Manfred Spraul <manfred@colorfullife.com>
Subject: Re: [PATCH V4 1/1] rcu: introduce kfree_rcu()
Date: Tue, 15 Mar 2011 21:29:09 -0700 [thread overview]
Message-ID: <20110316042909.GG2273@linux.vnet.ibm.com> (raw)
In-Reply-To: <4D802578.8050603@cn.fujitsu.com>
On Wed, Mar 16, 2011 at 10:50:32AM +0800, Lai Jiangshan wrote:
> On 03/15/2011 07:30 PM, Paul E. McKenney wrote:
> > On Tue, Mar 15, 2011 at 05:46:20PM +0800, Lai Jiangshan wrote:
> >> kfree_rcu() which was original proposed by Lai 2.5 years ago is one of
> >> the most important RCU TODO list entries, Lai and Manfred have worked on
> >> patches for this. This V4 patch is based on the Manfred's patch and
> >> the V1 of Lai's patch. (These two patches are almost the same
> >> in implementation, and this patch is mainly based on the Manfred's).
> >>
> >> Lai's V1 patch: http://lkml.org/lkml/2008/9/18/1
> >> Manfred's patch: http://lkml.org/lkml/2009/1/2/115
> >> RCU TODO list: http://www.kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
> >>
> >> This new introduced API kfree_rcu() primitive kfree()s the specified memory
> >> after a RCU grace period elapses.
> >>
> >> It replaces many simple "call_rcu(head, simple_kfree_callback)";
> >> These many simple_kfree_callback() instances just does
> >>
> >> kfree(containerof(head,struct whatever_struct,rcu_member));
> >>
> >> These simple_kfree_callback() instances are just duplicate code, we need
> >> a generic function for them.
> >>
> >> 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.)
> >
> > Thank you for putting this together! It does represent a nice
> > reduction in code size.
> >
> > Once it settles out a bit, I intend to queue this patch. It would be
> > best if the subsystems queue their own patches using kfree_rcu() once
> > this patch reaches mainline.
> >
>
> It seems that the subsystems maintainers just Ack the patches.
> I hope Ingo queue the Acked using kfree_rcu() patches into -tip,
> it will help the kfree_rcu() reaches mainline earlier.
Yep, I am comfortable pushing the patches that have received acks.
Thanx, Paul
next prev parent reply other threads:[~2011-03-16 4:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 9:46 [PATCH V4 1/1] rcu: introduce kfree_rcu() Lai Jiangshan
2011-03-15 10:15 ` Arnd Bergmann
2011-03-15 11:27 ` Paul E. McKenney
2011-03-15 12:02 ` Arnd Bergmann
2011-03-15 12:19 ` Paul E. McKenney
2011-03-15 13:07 ` Arnd Bergmann
2011-03-16 2:58 ` Lai Jiangshan
2011-03-16 4:38 ` Paul E. McKenney
2011-03-16 4:02 ` Paul E. McKenney
2011-03-18 3:15 ` [PATCH V5 " Lai Jiangshan
2011-03-18 8:14 ` Arnd Bergmann
2011-03-16 2:23 ` [PATCH V4 " Lai Jiangshan
2011-03-15 11:30 ` Paul E. McKenney
2011-03-16 2:50 ` Lai Jiangshan
2011-03-16 4:29 ` Paul E. McKenney [this message]
2011-03-15 13:11 ` Eric Dumazet
2011-03-16 4:03 ` Paul E. McKenney
2011-03-17 9:28 ` Lai Jiangshan
2011-03-17 17:50 ` Paul E. McKenney
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=20110316042909.GG2273@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@elte.hu \
/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.