All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gui,Jian" <guij@cn.ibm.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: systemtap@sources.redhat.com, nfs@lists.sourceforge.net
Subject: Re: [NFS] draft RPC tapset
Date: Wed, 06 Sep 2006 10:32:34 +0800	[thread overview]
Message-ID: <44FE3342.9050200@cn.ltcfwd.linux.ibm.com> (raw)
In-Reply-To: <44FD64CE.8080606@RedHat.com>

Steve Dickson wrote:
> 
> Question, should these probs be broken up into separate files?
> and if so, where do they need to live so they will be defined
> by the stap command?
> 
Thanks. I use a single file now since I was afraid each RPC
component uses a small file might mess up the systemtap tapset
dir. I will try to separate it if it becomes worse :-)

This is a generic tapset. You can use it like Frank said.

I am writing its LKET implementation so that we can use easier way
to provide more information, including common info(timestamp, pid,
cpu, etc) and trace hook specific data as well. Your suggestions
about which data should be recorded will be very appreciated.

-Gui,Jian

      reply	other threads:[~2006-09-06  2:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05  8:45 draft RPC tapset Gui,Jian
2006-09-05 11:51 ` Steve Dickson
2006-09-06  2:32   ` Gui,Jian [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=44FE3342.9050200@cn.ltcfwd.linux.ibm.com \
    --to=guij@cn.ibm.com \
    --cc=SteveD@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    --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 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.