From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "david m. richter" <richterd@citi.umich.edu>
Cc: Neil Brown <neilb@suse.de>, Peter Staubach <staubach@redhat.com>,
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 12:49:14 -0400 [thread overview]
Message-ID: <1185986954.6700.145.camel@localhost> (raw)
In-Reply-To: <Pine.BSO.4.64.0708011149240.25204@citi.umich.edu>
On Wed, 2007-08-01 at 11:59 -0400, david m. richter wrote:
> > david m. richter wrote:
> > > Hello, Neil,
> > >
> > > This set of patches adds -D/--diff-stat to nfsstat. When this flag is
> > > used, instead of printing out the current total statistics and exiting,
> > > nfsstat takes a snapshot of the current statistics and pauses until the user
> > > types ^C, at which point a second snapshot is taken and only the difference
> > > between the two is printed; i.e., only the statistics gathered during the
> > > pause.
> >
> > Hi.
> >
> > Perhaps I am missing something, but is something that we really need
> > to complicate the nfsstat support with? Is this not easy enough to
> > do with already existing tools or some easily written support in sh
> > or perl or awk or name your favorite administrative scripting language?
> >
> > Thanx...
> >
> > ps
>
>
> hello, peter,
>
> yes. :) right now, there's no easy way to run a test and get
> stats for just that test, since the counters persist -- so you have to do
> things like run a test, unmount, remount, etc. this is a quick way to get
> stats collected over an arbitrary period. and it's not very complicated,
> really.
>
> i don't think a shell/perl/python/etc script would be anywhere as
> useful a substitute. and with neil's suggestion about adding an optional
> timeout to make it easier to use -in- scripts, i think we're on the right
> track with this approach.
>
> .. thoughts/ideas?
How about instead just adding support for the 'nfsstat -z' option that
Solaris offers? That would make it easy to set up the type of script
that Peter is advocating.
All you need to do is to save a snapshot of the current /proc counters
in a file, then use that as the baseline for the output of future
nfsstat commands.
It might be an idea to also save /proc/sys/kernel/random/boot_id
somewhere in this 'baseline file' in order to be able to avoid files
that were created in a past boot instance.
Cheers
Trond
-------------------------------------------------------------------------
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 16:49 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 [this message]
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
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=1185986954.6700.145.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=chardson@umich.edu \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=richterd@citi.umich.edu \
--cc=soule@umich.edu \
--cc=staubach@redhat.com \
/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