linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: linux-nfs@vger.kernel.org
Subject: NFS daemon statistics in /proc/net/rpc/nfsd
Date: Fri, 5 Oct 2012 18:48:56 +0200	[thread overview]
Message-ID: <20121005184856.4472a72e@harpe.intellique.com> (raw)


I noticed a long time ago that the thread information in
/proc/net/rpc/nfsd isn't updated anymore since somewhere between the
2.629 (information present) and 2.6.32 (information missing). It's
quite easy to check:

# grep th /proc/net/rpc/nfsd
th 8 0 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000

All values are perpetually at zero. Unsurprising, because the
update_thread_usage function in fs/nfsd/nfssvc.c isn't present anymore.

I can't find any information about why this information was dropped; I
personnally found it useful to tune properly the number of nfs threads
on loaded servers. Did it use up too many resources? In that case,
could there be a mechanism to enable or disable therad information
gathering, for instance through writing to some /proc file?

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

             reply	other threads:[~2012-10-05 16:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 16:48 Emmanuel Florac [this message]
2012-10-05 18:42 ` NFS daemon statistics in /proc/net/rpc/nfsd Jim Rees
2012-10-05 20:28 ` J. Bruce Fields
2012-10-05 21:03   ` Emmanuel Florac

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=20121005184856.4472a72e@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --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).