From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 26/36] perf,rcu: convert call_rcu(free_ctx) to kfree_rcu()
Date: Fri, 18 Mar 2011 10:35:21 +0100 [thread overview]
Message-ID: <1300440921.21794.29.camel@twins> (raw)
In-Reply-To: <4D82DA8D.1000204@cn.fujitsu.com>
On Fri, 2011-03-18 at 12:07 +0800, Lai Jiangshan wrote:
>
> The rcu callback free_ctx() just calls a kfree(),
> so we use kfree_rcu() instead of the call_rcu(free_ctx).
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Please take them through whatever tree adds kfree_rcu() as that doesn't
seem to be part of any tree near me.
> ---
> kernel/perf_event.c | 10 +---------
> 1 files changed, 1 insertions(+), 9 deletions(-)
>
> diff --git a/kernel/perf_event.c b/kernel/perf_event.c
> index ed253aa..b0581bd 100644
> --- a/kernel/perf_event.c
> +++ b/kernel/perf_event.c
> @@ -584,14 +584,6 @@ static void get_ctx(struct perf_event_context *ctx)
> WARN_ON(!atomic_inc_not_zero(&ctx->refcount));
> }
>
> -static void free_ctx(struct rcu_head *head)
> -{
> - struct perf_event_context *ctx;
> -
> - ctx = container_of(head, struct perf_event_context, rcu_head);
> - kfree(ctx);
> -}
> -
> static void put_ctx(struct perf_event_context *ctx)
> {
> if (atomic_dec_and_test(&ctx->refcount)) {
> @@ -599,7 +591,7 @@ static void put_ctx(struct perf_event_context *ctx)
> put_ctx(ctx->parent_ctx);
> if (ctx->task)
> put_task_struct(ctx->task);
> - call_rcu(&ctx->rcu_head, free_ctx);
> + kfree_rcu(ctx, rcu_head);
> }
> }
>
prev parent reply other threads:[~2011-03-18 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 4:07 [PATCH 26/36] perf,rcu: convert call_rcu(free_ctx) to kfree_rcu() Lai Jiangshan
2011-03-18 9:35 ` 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=1300440921.21794.29.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.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.