From: Peter Staubach <staubach@redhat.com>
To: "david m. richter" <richterd@citi.umich.edu>
Cc: Neil Brown <neilb@suse.de>,
Andrew Richardson <chardson@umich.edu>,
nfs@lists.sourceforge.net, Alex Soule <soule@umich.edu>
Subject: Re: [PATCH 0/7] nfsstat: adding -D/--diff-stat to nfsstat
Date: Wed, 01 Aug 2007 14:22:19 -0400 [thread overview]
Message-ID: <46B0CF5B.1000609@redhat.com> (raw)
In-Reply-To: <Pine.BSO.4.64.0708011413000.25204@citi.umich.edu>
david m. richter wrote:
>> Now, if someone was proposing a way to do "nfsstat 5" and make the
>> output look useful, then I would be behind that 100%.
>>
>> Thanx...
>>
>> ps
>>
>
>
> do you mean "gather stats for the next 5 seconds"? i don't
> understand the arg.
Sorry, I should have been more explicit. I have wished for
something that would behave like "vmstat 5", ie. print nfsstat
statistics in some sort short hand fashion once every few
seconds, 5 in this example.
The problem has always been that there are too many operations
for summarize them on one line in any sort of interesting way.
This becomes particularly true for NFSv4 which has its multitude
of operations...
Perhaps we should just bite the bullet and produce the large
output, much like "iostat 5" seems to.
Thanx...
ps
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-01 18:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 21:38 [PATCH 0/7] nfsstat: adding -D/--diff-stat to nfsstat david m. richter
2007-07-31 22:11 ` Neil Brown
2007-07-31 23:29 ` david m. richter
2007-07-31 23:41 ` J. Bruce Fields
2007-08-01 0:42 ` Neil Brown
2007-08-01 11:55 ` Peter Staubach
2007-08-01 15:59 ` david m. richter
2007-08-01 16:49 ` Trond Myklebust
2007-08-01 17:07 ` J. Bruce Fields
2007-08-01 17:42 ` david m. richter
2007-08-01 16:50 ` J. Bruce Fields
2007-08-01 17:35 ` david m. richter
2007-08-01 17:41 ` J. Bruce Fields
2007-08-01 17:45 ` david m. richter
2007-08-01 17:46 ` Trond Myklebust
2007-08-01 17:48 ` david m. richter
2007-08-01 18:02 ` Trond Myklebust
2007-08-01 18:12 ` david m. richter
2007-08-01 18:15 ` Muntz, Daniel
2007-08-01 18:37 ` david m. richter
2007-08-01 18:41 ` Trond Myklebust
2007-08-01 18:47 ` david m. richter
2007-08-01 18:50 ` J. Bruce Fields
2007-08-01 20:03 ` Steve Dickson
2007-08-01 20:48 ` J. Bruce Fields
2007-08-01 21:50 ` Steve Dickson
2007-08-01 22:40 ` Trond Myklebust
2007-08-01 18:38 ` J. Bruce Fields
2007-08-01 17:52 ` J. Bruce Fields
2007-08-01 17:55 ` Peter Staubach
2007-08-01 18:14 ` david m. richter
2007-08-01 18:22 ` Peter Staubach [this message]
2007-08-01 18:25 ` david m. richter
2007-08-01 18:57 ` J. Bruce Fields
2007-08-01 19:35 ` Chuck Lever
2007-08-01 20:16 ` Steve Dickson
2007-08-01 20:54 ` Chuck Lever
2007-08-01 19:42 ` Steve Dickson
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=46B0CF5B.1000609@redhat.com \
--to=staubach@redhat.com \
--cc=chardson@umich.edu \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=richterd@citi.umich.edu \
--cc=soule@umich.edu \
/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.