From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Smets, Jan (Jan)" <jan.smets@alcatel-lucent.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS Server cache
Date: Mon, 19 Jul 2010 17:26:05 -0400 [thread overview]
Message-ID: <20100719212604.GA29058@fieldses.org> (raw)
In-Reply-To: <14C7F4F06DB5814AB0DE29716C4F6D670B7030B4@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
On Fri, Jun 25, 2010 at 12:57:05AM +0200, Smets, Jan (Jan) wrote:
> Hi list
>
> If I understood correctly, the main memory is used for caching NFS server data. Can I get more information on this? Statistics?
It uses the same caching as any other user of the exported filesystem.
What question exactly are you trying to answer?
> Is it possible to use a sort of fs-cache on the server? Thus using a SSD drive as cache for example. (at first sight fs-cache can only be used on the client side..)
If the nfs server code itself kept its own cache, that would cause
consistency problems between nfs clients and local users of the exported
filesystem.
So you want to solve the problem below the nfs level, in the vfs and/or
filesystem.
Making a filesystem use fs-cache requires modifying code of the
filesystem. I don't know whether it would make sense to do that for a
disk filesystem.
There might be some benefit to putting the journal on an ssd; see e.g.:
http://insights.oetiker.ch/linux/external-journal-on-ssd.html
> And maybe not so related: can I do data de-duplication? (within te
> cache? .. But I guess the FS should do that, but I could not find any
> capable of doing this on Linux.)
I believe people want btrfs to do deduplication some day.
--b.
prev parent reply other threads:[~2010-07-19 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 22:57 NFS Server cache Smets, Jan (Jan)
2010-07-19 21:26 ` J. Bruce Fields [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=20100719212604.GA29058@fieldses.org \
--to=bfields@fieldses.org \
--cc=jan.smets@alcatel-lucent.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 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.