From: David Howells <dhowells@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Steve Dickson <SteveD@redhat.com>,
nfs@lists.sourceforge.net,
Linux filesystem caching discussion list
<linux-cachefs@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NFS using CacheFS
Date: Tue, 05 Oct 2004 11:01:19 +0100 [thread overview]
Message-ID: <6047.1096970479@redhat.com> (raw)
In-Reply-To: <1096926837.22446.141.camel@lade.trondhjem.org>
> This is my one and only real gripe about it. The posix mount option is
> clearly documented, so we really cannot play around with it. Why can't
> you just add a separate cachefs flag?
That's just for the prototype. It will be changed later. It's also a stand-in
for the superblock un-aliasing patch.
> I'm a bit worried about the use of the raw IP address in
> nfs_cache_server_match(). It seems to me that when we add the NFSv4.1
> support for trunking over several different transport mechanisms (RDMA,
> IPv4/v6 etc) on the same mountpoint, then we may end up with a problem. We
> can probably leave it in for now, but later we may want to consider
> switching to using server->hostname or something equivalent.
There needs to be some way of matching NFS file handle sets in the cache if
you want persistant caches. The only way I could see was to use IP addr and
port number for NFS.
However, changing this later is trivial. If you bump the version number in the
netfs definition, then cachefs will nuke existing data in the cache that isn't
of the expected format.
David
next prev parent reply other threads:[~2004-10-05 10:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 20:45 [PATCH] NFS using CacheFS Steve Dickson
2004-10-04 21:53 ` Trond Myklebust
2004-10-04 21:53 ` Trond Myklebust
2004-10-05 10:01 ` David Howells [this message]
2004-10-08 4:36 ` Clemens Schwaighofer
2004-10-08 9:02 ` [Linux-cachefs] " David Howells
2004-10-08 11:22 ` Steve Dickson
2004-10-08 15:39 ` Clemens Schwaighofer
2004-10-11 14:23 ` Martin Waitz
2004-10-11 14:23 ` Martin Waitz
2004-10-11 15:18 ` David Howells
2004-10-11 15:18 ` [Linux-cachefs] " David Howells
2004-10-11 15:30 ` Trond Myklebust
2004-10-11 15:30 ` Trond Myklebust
2004-10-11 20:31 ` accessing/modifiying the nfs share files as different users bruce
2004-10-13 10:40 ` Re: [PATCH] NFS using CacheFS David Howells
2004-10-13 10:40 ` [Linux-cachefs] " David Howells
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=6047.1096970479@redhat.com \
--to=dhowells@redhat.com \
--cc=SteveD@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--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 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.