From: "Charles 'Boyo" <charlesboyo@gmail.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
Chuck Lever <chuck.lever@oracle.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Questions abou nfsd file cache and open files
Date: Fri, 29 Nov 2013 12:21:08 +0100 [thread overview]
Message-ID: <CAPD_G3JioWUiBJD-SMZeMgQd40DarVV_bYAnggQKgWLi3bQPCw@mail.gmail.com> (raw)
Hello all.
Please guide me into to find out the impact a busy nfsd is having on
the Linux page cache. Is it possible to determine which files have
portions in the page cache?
Secondly, files opened by nfs clients do not show up in lsof (or ftop)
on the nfs server? Is there any way to list these open files and more
importantly, observe the i/o to them?
Charles
next reply other threads:[~2013-11-29 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 11:21 Charles 'Boyo [this message]
2013-12-02 16:46 ` Questions abou nfsd file cache and open files Chuck Lever
2013-12-02 16:50 ` J. Bruce Fields
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=CAPD_G3JioWUiBJD-SMZeMgQd40DarVV_bYAnggQKgWLi3bQPCw@mail.gmail.com \
--to=charlesboyo@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.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).