All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Jordi Prats <jprats@cesca.es>
Cc: nfs@lists.sourceforge.net, csmithere@gmail.com
Subject: Re: about /proc/net/rpc/nfsd
Date: Tue, 23 Oct 2007 14:09:58 -0400	[thread overview]
Message-ID: <471E38F6.7000006@oracle.com> (raw)
In-Reply-To: <471E28AA.9010501@cesca.es>

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

Jordi Prats wrote:
> Hi,
> What would you thing about creating a nfsd man page on section 5 with 
> what does it mean every value?
> 
> I think on wiki pages should go how to interpret to enhance performance, 
> but not the meaning of every value you can get on statistics.
> 
> So, I'm thinking this as two different things to answer the following 
> questions:
> - What is this value? (on a man page)
> - How do I interpret this value to enhance performance? (on wiki's page 
> about performance)
> 
> What do you think?

I don't have any objection to that.  What would you call it: nfsd(7)? 
I'm not sure in which man section proc files are documented.

> Chuck Lever wrote:
>> Gabriel Barazer wrote:
>>> On 10/22/2007 11:36:56 PM +0200, Jordi Prats <jprats@cesca.es> wrote:
>>>> Hi all,
>>>> I've been researching the meaning of the contents of the 
>>>> /proc/net/rpc/nfsd file using the 2.6.23 kernel sources.
>>>>
>>>>
>>>> Sorry for this so long mail... That's all what I've got reading the 
>>>> source files. There's anything incorrect? There's some "educated 
>>>> guests"   So, could anyone please confirm or refute them?
>>>>
>>>> If you what me to do something with this I'd be glad of it!
>>>
>>> Wow this is an awesome job you've done here to document precisely 
>>> this proc file. I've tagged your mail and copied it in a safe place.  
>>> I'm sure this would be very useful to keep a place where all these 
>>> proc files are explained like this, maybe on the linux-nfs wiki ?
>>
>> This belongs in the NFS server performance chapter of the NFS How-To. 
>> The How-To's maintainer is csmithere@gmail.com.


[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 315 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
email;internet:chuck dot lever at nospam oracle dot com
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2007-10-23 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 21:36 about /proc/net/rpc/nfsd Jordi Prats
2007-10-22 21:54 ` Jordi Prats
2007-10-22 22:02 ` Gabriel Barazer
2007-10-23 15:07   ` Chuck Lever
2007-10-23 17:00     ` Jordi Prats
2007-10-23 18:09       ` Chuck Lever [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=471E38F6.7000006@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=csmithere@gmail.com \
    --cc=jprats@cesca.es \
    --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.