mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dbueso@suse.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Tuan Bui <tuan.d.bui@hp.com>,
	linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
	paulus@samba.org, acme@kernel.org, artagnon@gmail.com,
	jolsa@redhat.com, dvhart@linux.intel.com,
	Aswin Chandramouleeswaran <aswin@hp.com>,
	Jason Low <jason.low2@hp.com>,
	akpm@linux-foundation.org
Subject: Re: [RFC PATCH] Perf Bench: Locking Microbenchmark
Date: Thu, 02 Oct 2014 21:52:52 -0700	[thread overview]
Message-ID: <1412311972.27162.3.camel@linux-t7sj.site> (raw)
In-Reply-To: <20141001052832.GA32248@gmail.com>

On Wed, 2014-10-01 at 07:28 +0200, Ingo Molnar wrote:
> If you compare an strace of AIM7 steady state and 'perf bench 
> lock' steady state, is it comparable, i.e. do the syscalls and 
> other behavioral patterns match up?

With more than 1000 users I'm seeing:

-  33.74%    locking-creat  [kernel.kallsyms]              [k] mspin_lock                                                                                                ◆
   + mspin_lock                                                                                                                                                          ▒
   + __mutex_lock_slowpath                                                                                                                                               ▒
   + mutex_lock                                                                                                                                                          ▒
-   7.97%    locking-creat  [kernel.kallsyms]              [k] mutex_spin_on_owner                                                                                       ▒
   + mutex_spin_on_owner                                                                                                                                                 ▒
   + __mutex_lock_slowpath                                                                                                                                               ▒
   + mutex_lock                                                                                                     

Lower users count just shows the syscall entries.

Of course, the aim7 setup was running on a ramdisk, thus avoiding any IO
overhead in the traces.

Thanks,
Davidlohr


  parent reply	other threads:[~2014-10-03  4:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 23:49 Tuan Bui
2014-10-01  5:28 ` Ingo Molnar
2014-10-01 17:12   ` Arnaldo Carvalho de Melo
2014-10-03  4:57     ` Davidlohr Bueso
2014-10-08 22:14       ` Tuan Bui
2014-10-08 22:11     ` Tuan Bui
2014-10-03  4:52   ` Davidlohr Bueso [this message]
2014-10-08 22:13   ` Tuan Bui
2014-10-09  7:21     ` Ingo Molnar

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=1412311972.27162.3.camel@linux-t7sj.site \
    --to=dbueso@suse.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=artagnon@gmail.com \
    --cc=aswin@hp.com \
    --cc=dvhart@linux.intel.com \
    --cc=jason.low2@hp.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulus@samba.org \
    --cc=tuan.d.bui@hp.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
Powered by JetHome