From: Nathan DeBardeleben <ndebard@lanl.gov>
To: Hien Nguyen <hien@us.ibm.com>
Cc: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: Re: Evaluating SystemTap for Network Response Times
Date: Wed, 08 Feb 2006 16:23:00 -0000 [thread overview]
Message-ID: <43EA1AE9.2050700@lanl.gov> (raw)
In-Reply-To: <43E7E70A.2050502@us.ibm.com>
I appreciate all the help getting my feet off the ground. What you sent
me works perfectly, however, I want to understand it a bit more (of course).
I guess I have some basic questions about ST. For instance, I tried
running the 'top2.stp' David Sperry included in the list and that gives
me errors about resolving kernel.syscall.*. I'm guessing it has
something to do with a syscall tapset, but where do I go about getting
those? And further more, how do I know I need them?
What really is a 'tapset'? Is it just a collection of useful functions
that users might want to call that you put into a nice location so as to
keep from copying the code raw into each script that needs it? Or is it
something more?
And when I look at David's output it doesn't look like he pointed at an
include directory. Just really confused.
I know, lots of questions and I'm sure questions that would be in a nice
document if this weren't a project under such heavy development.
Thanks all. I apologize for the newbie questions, I'll get there soon. :)
-- Nathan
Correspondence
---------------------------------------------------------------------
Nathan DeBardeleben, Ph.D.
Los Alamos National Laboratory
Parallel Tools Team
High Performance Computing Environments
phone: 505-667-3428
email: ndebard@lanl.gov
---------------------------------------------------------------------
Hien Nguyen wrote:
> Hi Nathan,
>
> There are actually two seperate files
> 1. tcp_mon.stp
> 2. tcp_tapset/tapset.stp
>
> I include in this mail a tar file for those file for your convenience.
> Create a tmp directory,
> cd tmp, untar the file and run
> stap -I./tcp_tapset tcp_mon.stp (as root)
>
> Thanks, Hien.
>
> Nathan DeBardeleben wrote:
>
>> Hien Nguyen wrote:
>>
>>> Hi Nathan,
>>>
>>> I think what you are trying to achieve could be done with systemtap.
>>> I wrote a small script to monitor the tcp traffic a while back (see
>>> URL below)
>>> http://sourceware.org/ml/systemtap/2005-q4/msg00302.html
>>>
>> I'm a complete newbie to systemtap, so please explain why when I try
>> and run the example on the link above that you sent me I get this:
>>
>>> [root@kraken1 systemtap]# stap -v tcp_mon.stp
>>> Created temporary directory "/tmp/stapM6VSNS"
>>> parse error: embedded code in unprivileged script
>>> saw: embedded-code at tcp_mon.stp:70:1
>>> 1 parse error(s).
>>> Searched
>>> '/usr/share/systemtap/tapset/2.6.14-1.1656_FC4smp/x86_64/*.stp',
>>> match count 0
>>> Searched '/usr/share/systemtap/tapset/2.6.14-1.1656_FC4smp/*.stp',
>>> match count 0
>>> Searched '/usr/share/systemtap/tapset/2.6.14/x86_64/*.stp', match
>>> count 0
>>> Searched '/usr/share/systemtap/tapset/2.6.14/*.stp', match count 1
>>> Searched '/usr/share/systemtap/tapset/2.6/x86_64/*.stp', match count 0
>>> Searched '/usr/share/systemtap/tapset/2.6/*.stp', match count 0
>>> Searched '/usr/share/systemtap/tapset/x86_64/*.stp', match count 0
>>> Searched '/usr/share/systemtap/tapset/*.stp', match count 8
>>> Pass 1: parsed user script and 9 library script(s).
>>> Pass 1: parse failed. Running rm -rf /tmp/stapM6VSNS
>>> [root@kraken1 systemtap]#
>>
>> Also you say to copy tapset.stp to a directory you create in that
>> post - where do I get tapset.stp?
>>
>> Sorry for the beginner question :)
>>
>> -- Nathan
>> Correspondence
>> ---------------------------------------------------------------------
>> Nathan DeBardeleben, Ph.D.
>> Los Alamos National Laboratory
>> Parallel Tools Team
>> High Performance Computing Environments
>> phone: 505-667-3428
>> email: ndebard@lanl.gov
>> ---------------------------------------------------------------------
>>
>>
>
next prev parent reply other threads:[~2006-02-08 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 16:52 Nathan DeBardeleben
2006-01-31 17:21 ` Frank Ch. Eigler
2006-01-31 18:29 ` Nathan DeBardeleben
2006-01-31 17:30 ` Hien Nguyen
2006-02-06 22:55 ` Nathan DeBardeleben
2006-02-07 0:17 ` Hien Nguyen
2006-02-08 16:23 ` Nathan DeBardeleben [this message]
2006-02-08 17:25 ` Hien Nguyen
2006-02-08 17:58 ` Frank Ch. Eigler
2006-01-31 18:29 Frank Ch. Eigler
2006-01-31 18:44 ` Nathan DeBardeleben
2006-02-02 15:24 ` Frank Ch. Eigler
2006-02-07 9:54 David A Sperry
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=43EA1AE9.2050700@lanl.gov \
--to=ndebard@lanl.gov \
--cc=hien@us.ibm.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).