From: Masami Hiramatsu <hiramatu@sdl.hitachi.co.jp>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: [SAMPLE][PATCH 1/3]BTI: Binary Transport Interface for SystemTap
Date: Fri, 16 Dec 2005 05:37:00 -0000 [thread overview]
Message-ID: <43A24A66.7040405@sdl.hitachi.co.jp> (raw)
In-Reply-To: <y0md5jyply8.fsf@tooth.toronto.redhat.com>
Hi, Frank
Frank Ch. Eigler wrote:
> hiramatu wrote:
>>[...] The systemtap script with BTI (*1) has about 1.4 micro secs
>>of processing time. The systemtap script with ATI (*2) has about 4
>>micro secs of processing time. [...]
>
>>(*2)
>>probe kernel.function("sys_gettimeofday") {
>> log(string(get_tsc()) . string(get_cpu()) . string(pid()) . string(1)=
>> .
>>string(2). string(3). string(4). string(5));
>>}
>
> With the newer "print" statements, this expression is no longer state of the
> art. How would this compare?
OK. I measured the script using printf(). And the processing time is
about 2.6 micro secs. So, I expects BTI still has low overhead.
> printf("%d %d %d %d %d %d %d\n", get_tsc() /* we have that? */,
> get_cpu(), pid(), 1, 2, 3, 4, 5);
Oh, I forgot to write these functions. They are here:
function get_tsc:long () %{
rdtscll(THIS->__retvalue);
%}
function get_cpu:long () %{
THIS->__retvalue = smp_processor_id();
%}
--
Masami HIRAMATSU
2nd Research Dept.
Hitachi, Ltd., Systems Development Laboratory
E-mail: hiramatu@sdl.hitachi.co.jp
prev parent reply other threads:[~2005-12-16 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 8:21 Masami Hiramatsu
2005-12-15 16:38 ` Frank Ch. Eigler
2005-12-16 5:37 ` Masami Hiramatsu [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=43A24A66.7040405@sdl.hitachi.co.jp \
--to=hiramatu@sdl.hitachi.co.jp \
--cc=fche@redhat.com \
--cc=systemtap@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).