Linux NFS development
 help / color / mirror / Atom feed
From: Li Guanglei <guanglei@cn.ibm.com>
To: Chuck Lever <chucklever@gmail.com>
Cc: "systemtap@sourceware.org" <systemtap@sourceware.org>,
	        nfs@lists.sourceforge.net
Subject: Re: [NFS] [ltc-perf] draft of nfs event hook
Date: Fri, 28 Jul 2006 06:47:02 +0800	[thread overview]
Message-ID: <44C94266.6070606@cn.ibm.com> (raw)
In-Reply-To: <76bd70e30607270829q500711c8k8e7dd6ba9a9b6dfe@mail.gmail.com>

> 
> 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.
> 
> 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?
> 
>>
>>    What I didn't list about NFS operations includes authentication,
>> NFSv4 callback and RPC(I prefer to use a separate set of trace hooks
>> for RPC). I am not sure if these operations are also required to be
>> traced. If I missed some important functions or I listed some
>> redundant functions, please feel free to let me know. Any comments
>> will be highly appreciated.
>>

I didn't list RPC here because I think RPC is not only used by NFS and 
I need another set of RPC trace hooks to address the RPC server and 
client side operations. That will be my plan of the next set of trace 
hooks.

- Guanglei

  parent reply	other threads:[~2006-07-27 22:47 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
2006-07-27 22:47     ` Li Guanglei [this message]
     [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=44C94266.6070606@cn.ibm.com \
    --to=guanglei@cn.ibm.com \
    --cc=chucklever@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox