All of lore.kernel.org
 help / color / mirror / Atom feed
From: "G. Allen Morris III" <gam3-nfs@gam3.net>
To: nfs@lists.sourceforge.net
Subject: [RFC] nfsstat v4 layout
Date: Wed, 16 Mar 2005 12:37:59 -0500	[thread overview]
Message-ID: <20050316173759.GA4360@gam3.net> (raw)


I made a patch to nfsstat to display v4 stats.
I am having a problem with some of the names being so
long setclientid_confirm for instance.  

Is the format below too confusing?  Anyone have a better idea?

Client nfs v4:
null        read        write       commit      open        *_confirm   
0       0%  0       0%  0       0%  0       0%  0       0%  0       0%  
*_noattr    *_downgrade close       setattr     fsinfo      renew       
0       0%  0       0%  0       0%  0       0%  0       0%  0       0%  
setclientid *_confirm   lock        lockt       locku       access      
0       0%  0       0%  0       0%  0       0%  0       0%  0       0%  
getattr     lookup      lookup_root remove      rename      link        
0       0%  0       0%  0       0%  0       0%  0       0%  0       0%  
symlink     create      pathconf    statfs      readlink    readdir     
0       0%  0       0%  0       0%  0       0%  0       0%  0       0%  
server_caps delegreturn 
0       0%  0       0%  


Allen Morris <gam3@gam3.net>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2005-03-16 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 17:37 G. Allen Morris III [this message]
2005-03-16 22:33 ` [RFC] nfsstat v4 layout G. Allen Morris III
  -- strict thread matches above, loose matches on Subject: below --
2005-03-16 18:05 Lever, Charles

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=20050316173759.GA4360@gam3.net \
    --to=gam3-nfs@gam3.net \
    --cc=nfs@lists.sourceforge.net \
    /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.