All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jose R. Santos" <jrs@us.bim.com>
To: Chuck Lever <chucklever@gmail.com>
Cc: Li Guanglei <guanglei@cn.ibm.com>,
	        "systemtap@sourceware.org" <systemtap@sourceware.org>,
	        nfs@lists.sourceforge.net
Subject: Re: [NFS] [ltc-perf] draft of nfs event hook
Date: Thu, 27 Jul 2006 12:01:09 -0500	[thread overview]
Message-ID: <44C8F155.5000000@us.bim.com> (raw)
In-Reply-To: <76bd70e30607270829q500711c8k8e7dd6ba9a9b6dfe@mail.gmail.com>

Chuck Lever wrote:
> On 7/27/06, Li Guanglei <guanglei@cn.ibm.com> wrote:
>>    When we started working on NFS trace hooks, we realized it is not
>> an easy task. Although we use NFS in daily work but we don't have much
>> knowledge about the NFS protocol details and its implementation inside
>> the Kernel. So I divided the work into two steps. At the first step I
>> need get a list of trace points. And at the second step I need to make
>> sure what trace data is available for each trace hook. In a short, the
>> trace data available for each hook will be derived from the arguments
>> of the kernel functions being probed.
>>
>>    We read through the Kernel source code and chose some functions to
>> be instrumented. We will trace the entry of these functions and if
>> necessary, the return of them will also be traced. The following is
>> the list of these functions, please take a review:
>
> Have you done this with a local file system?  I assume yes, and that
> you just described the general approach you have taken with other file
> systems.  I think getting the same kind of data and trace points from
> the NFS client as you added to local file systems would be good.

There is someone already working on a tapset for ext3 and we are waiting 
for that tapset to be available before we go into looking how to add 
trace hooks to ext3.  We plan to have a similar approach to the NFS hooks.
>
> Capturing VFS and address space entry points is definitely useful and
> is similar to local file systems.  At the bottom of the NFS client is
> the RPC client, and it acts just like the block I/O layer does for
> local file systems.  Would you consider adding trace points in the
> LKET for the RPC client and server?

Definitely.  We've already added a trace hook on the NFS server dispatch 
entry and exit and we are looking at adding even more.  While our focus 
has mostly been adding hooks that would assist in performance analysis, 
the tool can also be used for the purposes of debugging as well.  If you 
have specific places where you would like to see trace hook inserted, we 
are definitely interested.

-JRS

  reply	other threads:[~2006-07-27 17:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26  9:13 [ltc-perf] draft of nfs event hook Xue Peng Li
2006-07-26  9:13 ` Christoph Hellwig
2006-07-26 13:50 ` Chuck Lever
2006-07-28  3:35   ` Xue Peng Li
2006-07-27 13:57 ` Li Guanglei
2006-07-27 15:29   ` [NFS] " Chuck Lever
2006-07-27 17:01     ` Jose R. Santos [this message]
2006-07-27 22:47     ` Li Guanglei
     [not found]       ` <001301c6b1e8$bd7cf590$160b0a0a@ict25eacacc325>
2006-07-28  2:03         ` Li Guanglei
2006-08-11  1:57   ` Xue Peng Li
2006-08-16  8:56     ` Xue Peng Li
2006-08-22 10:08       ` Xue Peng Li

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=44C8F155.5000000@us.bim.com \
    --to=jrs@us.bim.com \
    --cc=chucklever@gmail.com \
    --cc=guanglei@cn.ibm.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=systemtap@sourceware.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.