linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Kevin Constantine
	<Kevin.Constantine-FfNkGbSheRGpB8w63BLUukEOCMrvLtNR@public.gmane.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 3/3] nfsstat: Eliminate the displaying zero stats
Date: Mon, 13 Apr 2009 17:28:45 -0400	[thread overview]
Message-ID: <49E3AE8D.70302@RedHat.com> (raw)
In-Reply-To: <49E3701E.40202-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>



Kevin Constantine wrote:
> Steve Dickson wrote:
>> Hey Bruce,
>>
>> J. Bruce Fields wrote:
>>> On Wed, Apr 08, 2009 at 12:05:08PM -0400, Steve Dickson wrote:
>>>> Eliminate the displaying zero stats when the explicit protocol
>>>> is specified (-2, -3, -4) the -Z and or --list options.
>>>>     When a particular protocol is specified and either
>>>> the -Z or --list options are used, zeros or blank lines
>>>> are echoed to the screen when there is not any NFS traffic.
>>>> This cause any useful data to be scroll off the screen.
>>> Sound like good fixes.
>>>
>>>>     With this patch only non-zero stats will be shown, which
>>>> makes the output of these options more condensed and
>>>> in turn more useful.
>>> Couldn't this make the output harder to parse?  E.g. if you want to know
>>> how many getattr's were sent each second, it might be simpler if you say
>>> a 0 those times when there were no getattrs.
>>>
>> Maybe.. but if one was parsing the output and the parser didn't see a
>> gettr stat, I'm assuming it would not increment the "gettr counter"
>> so it would be know there were zero gettars in that time period..
>> The main reason I did this was, when watching reads and writes, 90% of
>> the output was zeros stats which made very difficult to see the non
>> zero counts (i.e. read and write stats) since they generally got
>> scrolled of the screen...
>> Also note, when the --list option is not used, zero stats are shown in
>> the column output, but granted, the column output
>> is a bit harder to parse than the list output.
>>
>> I guess I could change it so non zero stats are show only the --sleep
>> option is *not* used.... 
> 
> Dare I suggest another commandline argument?  I didn't really like the
> idea of leaving out the stats with 0's, but after trying it, the output
> does look a lot cleaner.  Perhaps giving users the choice would be the
> way to go.
hmm.. I'm not sure yet another flag would be good...

I guess I like the idea of having the output show what happen 
instead of what has not happen... also remember, the non list output
will show the zeros... But I'm open for compromise... 

steved.
 

      parent reply	other threads:[~2009-04-13 21:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 14:51 [PATCH 0/3] nfsstat: Fixing and improving the new --sleep and --list options Steve Dickson
     [not found] ` <49DCB9DA.5000300-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-04-08 16:01   ` [PATCH 1/3] nfsstat: The --list option does not work on server stats Steve Dickson
2009-04-08 16:03   ` [PATCH 2/3] nfsstat: -Z showing incorrect " Steve Dickson
2009-04-08 16:05   ` [PATCH 3/3] nfsstat: Eliminate the displaying zero stats Steve Dickson
     [not found]     ` <49DCCB34.4080901-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-04-12 17:23       ` J. Bruce Fields
2009-04-13 12:08         ` Steve Dickson
     [not found]           ` <49E32B4B.5060704-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-04-13 17:02             ` Kevin Constantine
     [not found]               ` <49E3701E.40202-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>
2009-04-13 21:28                 ` Steve Dickson [this message]

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=49E3AE8D.70302@RedHat.com \
    --to=steved@redhat.com \
    --cc=Kevin.Constantine-FfNkGbSheRGpB8w63BLUukEOCMrvLtNR@public.gmane.org \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).