linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: Cachefiles question
Date: Fri, 08 May 2009 15:11:07 +0100	[thread overview]
Message-ID: <9390.1241791867@redhat.com> (raw)
In-Reply-To: <20090508125425.GK18351@ics.muni.cz>

Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote:

> what is fscache newly added into mainline supposed to do?
> 
> I thought it is used as writeback cache and read cache for network file
> systems. But it appears that it does not do any writeback and it seems it
> caches only few reads.

It only caches files on NFS that are opened for reading at the moment due to
coherency issues.

> however, after the build is complete:
> /opt/fscache# du -sm
> 2	.

Is there anything in dmesg?

And can you check /proc/fs/fscache/stats?

David

      reply	other threads:[~2009-05-08 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 12:54 Cachefiles question Lukas Hejtmanek
2009-05-08 14:11 ` David Howells [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=9390.1241791867@redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=xhejtman@ics.muni.cz \
    /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).