From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Ming Lei <tom.leiming@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: lock's trace events can improve mutex's performance in userspace?
Date: Thu, 11 Mar 2010 17:43:44 +0800 [thread overview]
Message-ID: <4B98BB50.1000002@cn.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
We found that if enable lock's trace events, the 'sysbench mutex'
benchmark program can run quicker.
The simple program that is attached can reproduce it, the system info,
kernel config, and the script are also attached.
The test step is below:
# tar -zxvf test-mutex.tar.bz
# cd test-mutex
# make
# ./tscript.sh >& log
# cat log | grep "real"
real 0m46.765s < all trace events are disabled >
real 0m47.073s
real 0m47.402s
real 0m46.458s
real 0m47.433s
real 0m47.395s
real 0m47.010s
real 0m47.454s
real 0m47.044s
real 0m47.464s
real 0m39.245s < enable lock's trace events >
real 0m40.822s
real 0m40.779s
real 0m40.549s
real 0m40.605s
real 0m40.923s
real 0m40.560s
real 0m41.050s
real 0m40.757s
real 0m40.715s
[ "< ... >" is my comments ]
>From the result, we can see the program's runtime is less if enable lock's
trace events.
The conclusion is weird but i don't know why.
[-- Attachment #2: test-mutex.tar.bz --]
[-- Type: application/octet-stream, Size: 23996 bytes --]
next reply other threads:[~2010-03-11 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 9:43 Xiao Guangrong [this message]
2010-03-13 4:27 ` lock's trace events can improve mutex's performance in userspace? Hitoshi Mitake
2010-04-05 9:14 ` Michel Lespinasse
2010-04-08 9:05 ` Xiao Guangrong
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=4B98BB50.1000002@cn.fujitsu.com \
--to=xiaoguangrong@cn.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tom.leiming@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