linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	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>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 0/6] rcu: introduce kfree_rcu V2
Date: Wed, 4 Mar 2009 12:45:04 +0100	[thread overview]
Message-ID: <20090304114504.GB4916@elte.hu> (raw)
In-Reply-To: <49AE484C.8020801@cn.fujitsu.com>


* Lai Jiangshan <laijs@cn.fujitsu.com> wrote:

> Ingo Molnar wrote:
> > 
> > Nice idea. The patches dont actually remove the RCU helpers 
> > anywhere. Might be useful to include a few example conversions 
> > of this facility as well, so that the total impact can be seen.
> > 
> > 
> 
> This is one of patches I test kfree_rcu().
> And it could be an example conversions of this facility.
> 
> ---
>  arch/ia64/sn/kernel/irq.c           |   14 +-----------
>  block/genhd.c                       |   10 --------
>  ipc/sem.c                           |   10 +-------
>  kernel/audit_tree.c                 |    8 ------
>  kernel/cgroup.c                     |    9 -------
>  kernel/smp.c                        |   11 ---------
>  mm/vmalloc.c                        |   18 +--------------
>  net/can/af_can.c                    |   14 +-----------
>  net/core/gen_estimator.c            |    9 -------
>  net/core/net_namespace.c            |   10 --------
>  net/ipv4/fib_trie.c                 |    7 ------
>  net/ipv6/addrconf.c                 |   10 --------
>  net/netfilter/nf_conntrack_extend.c |    8 ------
>  net/netlabel/netlabel_unlabeled.c   |   42 +-----------------------------------
>  security/device_cgroup.c            |   10 --------
>  security/keys/keyring.c             |   15 ------------
>  security/keys/user_defined.c        |   18 +--------------
>  security/selinux/netif.c            |   18 ---------------
>  security/selinux/netnode.c          |   20 +----------------
>  security/selinux/netport.c          |   20 +----------------
>  20 files changed, 28 insertions(+), 253 deletions(-)

Looks convincing to me but Nick does not like the extra SLAB 
field it uses :-/

	Ingo

  reply	other threads:[~2009-03-04 11:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 13:44 [PATCH -mm 0/6] rcu: introduce kfree_rcu V2 Lai Jiangshan
2009-03-03 14:09 ` Ingo Molnar
2009-03-04  9:22   ` Lai Jiangshan
2009-03-04 11:45     ` Ingo Molnar [this message]
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=20090304114504.GB4916@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --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).