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 <[email protected]>
-------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
mr morris-
i think open_cnfrm or open_conf makes sense as open_confirm. and so on
for the others:
open_dngrd; setclntid doesn't need to be spelled out, for instance.
also, i would love it if the count fields were wider (NFSv2 and v3 too).
> -----Original Message-----
> From: G. Allen Morris III [mailto:[email protected]]=20
> Sent: Wednesday, March 16, 2005 12:38 PM
> To: [email protected]
> Subject: [NFS] [RFC] nfsstat v4 layout
>=20
>=20
>=20
> 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. =20
>=20
> Is the format below too confusing? Anyone have a better idea?
>=20
> Client nfs v4:
> null read write commit open =20
> *_confirm =20
> 0 0% 0 0% 0 0% 0 0% 0 0% 0=20
> 0% =20
> *_noattr *_downgrade close setattr fsinfo =20
> renew =20
> 0 0% 0 0% 0 0% 0 0% 0 0% 0=20
> 0% =20
> setclientid *_confirm lock lockt locku =20
> access =20
> 0 0% 0 0% 0 0% 0 0% 0 0% 0=20
> 0% =20
> getattr lookup lookup_root remove rename =20
> link =20
> 0 0% 0 0% 0 0% 0 0% 0 0% 0=20
> 0% =20
> symlink create pathconf statfs readlink =20
> readdir =20
> 0 0% 0 0% 0 0% 0 0% 0 0% 0=20
> 0% =20
> server_caps delegreturn=20
> 0 0% 0 0% =20
>=20
>=20
> Allen Morris <[email protected]>
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from=20
> real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> NFS maillist - [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfs
>=20
-------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Wed, Mar 16, 2005 at 12:37:59PM -0500, G. Allen Morris III wrote:
>
> 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?
>
I increased the count to `-8d' and the rows are now 76 charaters
wide. To make them wider I would think about reducing to 5 columns
or making it dynamic (like ls).
I also changed the v4 names to abbreviations.
Allen
--
Server packet stats:
packets udp tcp tcpconn
0 3727 0 0
Server rpc stats:
calls badcalls badauth badclnt xdrcall
3730 0 0 0 0
Server reply cache:
hits misses nocache
0 0 3730
Server file handle cache:
lookup anon ncachedir ncachedir stale
0 0 0 0 1242
Server nfs v2:
null getattr setattr root lookup readlink
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
read wrcache write create remove rename
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
link symlink mkdir rmdir readdir fsstat
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
Server nfs v3:
null getattr setattr lookup access readlink
1 0% 0 0% 0 0% 0 0% 0 0% 0 0%
read write create mkdir symlink mknod
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
remove rmdir rename link readdir readdirplus
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
fsstat fsinfo pathconf commit
3729 99% 0 0% 0 0% 0 0%
Server nfs v4:
null compound
0 0% 0 0%
Client packet stats:
packets udp tcp tcpconn
0 0 0 0
Client rpc stats:
calls retrans authrefrsh
2 0 0
Client nfs v2:
null getattr setattr root lookup readlink
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
read wrcache write create remove rename
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
link symlink mkdir rmdir readdir fsstat
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
Client nfs v3:
null getattr setattr lookup access readlink
0 0% 1 50% 0 0% 0 0% 0 0% 0 0%
read write create mkdir symlink mknod
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
remove rmdir rename link readdir readdirplus
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
fsstat fsinfo pathconf commit
0 0% 1 50% 0 0% 0 0%
Client nfs v4:
null read write commit open open_conf
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
open_noat open_dgrd close setattr fsinfo renew
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
setclntid 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%
-------------------------------------------------------
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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs