From: "J. Bruce Fields" <bfields@fieldses.org>
To: Shankar Anand <shanand@novell.com>
Cc: nfs@lists.sourceforge.net, nfsv4@linux-nfs.org
Subject: Re: PATCH [1/2] Capture nfsv4 server operations statistics
Date: Fri, 19 May 2006 12:27:47 -0400 [thread overview]
Message-ID: <20060519162747.GI3721@fieldses.org> (raw)
In-Reply-To: <446E3040.AD69.00CC.0@novell.com>
On Fri, May 19, 2006 at 09:23:20AM -0600, Shankar Anand wrote:
> Verified compilation when nfsv4 is configured out. And also
> made changes so that the nfsv4 operation statistics are captured
> only when nfsv4 is configured.
Thanks! Looks fine to me.
One last thing I wonder about--the current /proc/net/rpc/nfsd ends with
lines like:
proc2 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc3 22 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc4 2 4 172
where the two operations counted on the last line are NULL and COMPOUND.
You're appending one more line, to make:
proc2 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc3 22 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc4 2 4 172
proc4ops 37 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
I like the fact that that doesn't bother the preexisting proc4 line. On
the other hand, as far as we know nobody's ever used the data on that
line, and it's hard to see how they would in the future (the number of
NULL calls to the server isn't very important), so may it would be
simplest just to replace the proc4 line entirely, as was done on the
client side.
Any strong opinions from anyone else?
--b.
next prev parent reply other threads:[~2006-05-19 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4469C82B.AD69.00CC.0@novell.com>
2006-05-16 7:11 ` PATCH [1/2] Capture nfsv4 server operations statistics Shankar Anand
[not found] ` <20060517213638.GE11237@fieldses.org>
2006-05-19 15:23 ` Shankar Anand
2006-05-19 16:27 ` J. Bruce Fields [this message]
2006-05-20 8:07 ` Shankar Anand
2006-05-30 14:30 ` Shankar Anand
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=20060519162747.GI3721@fieldses.org \
--to=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
--cc=shanand@novell.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 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.