From: Steve Dickson <SteveD@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: interprtation of /proc/net/rpc/nfsd
Date: Tue, 12 Oct 2004 05:05:44 -0400 [thread overview]
Message-ID: <416B9E68.40009@RedHat.com> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C61130435E96A@lavender-fe.eng.netapp.com>
Lever, Charles wrote:
>>Well... zeroing out the nfs stats was something I proposed a
>>while ago but got shoot down both internally and externally
>>since zero out stats is "not the Linux way".... so I've taken
>>the patch out of both FC and RHEL kernels, but I guess I
>>forgot to take it out of the nfs-utils....
>>
>>
>
>for the record, the reason that zeroing the kernel stats is a bad idea
>is that this should really be a user-space thing. otherwise, if process
>A is sampling the stats and process B zeroes them, it will screw up
>process A's samples.
>
>
This make senses for stats that measure time based things like bit rate or
latency.... but for stats that measure simple activity, sampling does not
really come into play.... imho...
SteveD.
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-10-12 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 15:22 interprtation of /proc/net/rpc/nfsd Lever, Charles
2004-10-12 9:05 ` Steve Dickson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-08 10:09 Jehan PROCACCIA
2004-10-08 13:03 ` James Pearson
2004-10-08 13:28 ` Jehan PROCACCIA
2004-10-08 14:43 ` James Pearson
2004-10-08 15:46 ` Jehan PROCACCIA
2004-10-11 11:13 ` Steve Dickson
2004-10-11 13:01 ` Jehan PROCACCIA
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=416B9E68.40009@RedHat.com \
--to=steved@redhat.com \
--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.