From: Amit Tewari | gmail <tewari.a@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: FSCache and NFS Attribute caching
Date: Wed, 15 Jun 2011 11:04:52 +0530 [thread overview]
Message-ID: <4DF8447C.40409@gmail.com> (raw)
Hi,
fscache is being considered to be deployed with NFS 3 server in a
metadata rich environment (millions of small files, with very low rate
of file data change). At present actimeo=600 is used with NFS mount
options (without fscache), to cache file attributes. I am not clear on
1. How FSCache handles meta data caching?
2. Does FSCache consider actimeo values before making a request to server?
3. When FSCache has to do metadata lookup from server, does it check
local cache first and then server lookup is performed?
need some definitive answer. Nearest that i could find anything is:
http://kerneltrap.org/Linux/Local_Caching_For_Network_Filesystems
http://linux-nfs.org/pipermail/nfsv4/2006-August/004844.html (for NFS v4)
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/fscachelimitnfs.html
Ultimate goal is to reduce metadata lookup load from the NFS server. Any
clarity/ pointers/ help will be highly appreciated.
Thanks in advance.
Regards
Amit
reply other threads:[~2011-06-15 5:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DF8447C.40409@gmail.com \
--to=tewari.a@gmail.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).