linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-fsdevel@vger.kernel.org, linux-cachefs@redhat.com
Subject: Re: [PATCH][RFC] NFS: Adding hooks to enable the use of FS-Cache
Date: Fri, 21 Apr 2006 11:42:29 -0400	[thread overview]
Message-ID: <4448FD65.7060007@RedHat.com> (raw)
In-Reply-To: <1145633490.8150.17.camel@lade.trondhjem.org>

Trond Myklebust wrote:
> On Fri, 2006-04-21 at 11:14 -0400, Steve Dickson wrote:
> 
>>This patch (based on Trond's nfs-2.6 git tree) adds the hooks need to
>>allow NFS to use the generic filesystem caching facility FS-Cache.
>>Caching is done on a per mount bases. To activate caching, the 'fsc'
>>flag is need as a mount option.
>>Ex:
>>     mount -o fsc server:/export /mnt
>>
>>(binary and source rpms as well as the actual patch are available at
>>  http://people.redhat.com/steved/cachefs/util-linux/)
> 
> 
> Hmm... Are you sure that is based on the latest trees? 
Just this morning I did an git fetch on my cloned nfs-2.6
tree... and everything seem to apply just fine...

> AFAICS it shouldn't even apply to stock 2.6.17-rc2 since it doesn't take into
> account the fact that we already use PagePrivate()+nfs_invalidatepage in
> order to fix truncate races.
hmm... I did not see that... so there must a disconnect somewhere...

> Could you look into that please?
Will do...

steved.

  reply	other threads:[~2006-04-21 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 15:14 [PATCH][RFC] NFS: Adding hooks to enable the use of FS-Cache Steve Dickson
2006-04-21 15:31 ` Trond Myklebust
2006-04-21 15:42   ` Steve Dickson [this message]
2006-04-21 15:53     ` Trond Myklebust
2006-04-21 15:56       ` Steve Dickson
2006-04-21 15:44   ` [Linux-cachefs] " David Howells
  -- strict thread matches above, loose matches on Subject: below --
2006-04-21 15:47 Steve Dickson

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=4448FD65.7060007@RedHat.com \
    --to=steved@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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).