From: Christoph Lameter <cl@linux.com>
To: Shan Wei <shanwei88@gmail.com>
Cc: rostedt@goodmis.org, fweisbec@gmail.com, mingo@redhat.com,
Kernel-Maillist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] trace: use __this_cpu_inc/dec operation instead of __get_cpu_var
Date: Mon, 19 Nov 2012 21:34:57 +0000 [thread overview]
Message-ID: <0000013b1a987395-2afa8715-e3f8-4bd1-8f56-6a8073da757b-000000@email.amazonses.com> (raw)
In-Reply-To: <50A9C1BD.1060308@gmail.com>
On Mon, 19 Nov 2012, Shan Wei wrote:
> __this_cpu_inc_return() or __this_cpu_dec generates a single instruction,
> which is faster than __get_cpu_var operation.
Reviewed-by: Christoph Lameter <cl@linux.com>
next prev parent reply other threads:[~2012-11-19 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 5:21 [PATCH] trace: use __this_cpu_inc/dec operation instead of __get_cpu_var Shan Wei
2012-11-19 21:34 ` Christoph Lameter [this message]
2012-11-30 6:37 ` Shan Wei
2013-02-03 19:18 ` [tip:perf/core] tracing: Use __this_cpu_inc/ dec " tip-bot for Shan Wei
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=0000013b1a987395-2afa8715-e3f8-4bd1-8f56-6a8073da757b-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=shanwei88@gmail.com \
/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).