linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS daemon statistics in /proc/net/rpc/nfsd
Date: Fri, 5 Oct 2012 23:03:02 +0200	[thread overview]
Message-ID: <20121005230302.15ff87a8@galadriel.home> (raw)
In-Reply-To: <20121005202845.GB30139@fieldses.org>

Le Fri, 5 Oct 2012 16:28:45 -0400 vous écriviez:

> The trick to answering a question like this is:
> 
> 	git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> cd linux got log -p fs/nfsd/nfssvc.c

Yes, I realise there are several ways to search through the git
history, alas my git-fu is extremely limited because I'm still a
sectator of subversion :)

> There's a file /proc/fs/nfsd/pool_stats that should be useful for the
> same purpose; see the discussion in
> Documentation/filesystems/nfs/knfsd-stats.txt.
> 
> (But note the overloads-avoided number mentioned there had to be
> removed due to reports of a performance regression; we should figure
> out what to do about that.)
> 

Thank you very much, this looks very promising, and makes definitely
more sense than the bizarre decile-distribution of thread usage from
the old system.

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

      reply	other threads:[~2012-10-05 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 16:48 NFS daemon statistics in /proc/net/rpc/nfsd Emmanuel Florac
2012-10-05 18:42 ` Jim Rees
2012-10-05 20:28 ` J. Bruce Fields
2012-10-05 21:03   ` Emmanuel Florac [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=20121005230302.15ff87a8@galadriel.home \
    --to=eflorac@intellique.com \
    --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).