All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	"Frank Ch. Eigler" <fche@redhat.com>
Cc: "Kornievskaia, Olga" <Olga.Kornievskaia@netapp.com>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>
Subject: Re: timing information with perf
Date: Mon, 16 Nov 2015 20:57:34 -0700	[thread overview]
Message-ID: <564AA5AE.1020303@gmail.com> (raw)
In-Reply-To: <20151117001233.GC11993@kernel.org>

On 11/16/15 5:12 PM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Nov 16, 2015 at 01:08:15PM -0500, Frank Ch. Eigler escreveu:
>> Olga.Kornievskaia wrote:
>
>>> [...] say there are two tracepoints ?foobar_enter? and
>>> ?foobar_exit?. Each tracepoint logs a timestamp. I?d like to be able
>>> to say that on average it takes that many time-units between ?enter?
>>> and ?exit? tracepoints. [...]
>
>> For completeness, a complete systemtap implementation of this could look like:
>
>> # stap -e '
>>     global s, t%
>>     probe kernel.trace("foobar_enter") {
>>         t[tid()]=gettimeofday_us()
>>     }
>>     probe kernel.trace("foobar_exit") {
>>         if (tid() in t) { s <<< gettimeofday_us() - t[tid()] }
>>     }
>>     probe timer.s(5),end {
>>         printf("cumulative average us: %d\n", @avg(s))
>>     }
>> '
>
> Is that done syncronously?

Interesting solution. How does it scale with CPUs and tasks?

  parent reply	other threads:[~2015-11-17  3:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 21:07 timing information with perf Kornievskaia, Olga
2015-11-12 21:57 ` Arnaldo Carvalho de Melo
2015-11-12 22:04   ` Arnaldo Carvalho de Melo
2015-11-12 23:19     ` David Ahern
2015-11-12 23:09   ` Kornievskaia, Olga
2015-11-12 23:22     ` David Ahern
2015-11-12 23:34     ` Arnaldo Carvalho de Melo
2015-11-13 17:01       ` Kornievskaia, Olga
2015-11-13 19:47         ` Arnaldo Carvalho de Melo
2015-11-13 21:57           ` Kornievskaia, Olga
2015-11-16 18:08 ` Frank Ch. Eigler
2015-11-17  0:12   ` Arnaldo Carvalho de Melo
2015-11-17  0:30     ` Frank Ch. Eigler
2015-11-17  1:31       ` Arnaldo Carvalho de Melo
2015-11-17  3:57     ` David Ahern [this message]
2015-11-17 13:31       ` Frank Ch. Eigler
2015-11-17 13:39         ` Arnaldo Carvalho de Melo
2015-11-17 14:04           ` Frank Ch. Eigler

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=564AA5AE.1020303@gmail.com \
    --to=dsahern@gmail.com \
    --cc=Olga.Kornievskaia@netapp.com \
    --cc=acme@kernel.org \
    --cc=fche@redhat.com \
    --cc=linux-perf-users@vger.kernel.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.