Linux NFS development
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux filesystem caching discussion list
	<linux-cachefs@redhat.com>,
	nfs@lists.sourceforge.net, Martin Waitz <tali@admingilde.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Steve Dickson <SteveD@redhat.com>,
	Clemens Schwaighofer <cs@tequila.co.jp>
Subject: Re: Re: [PATCH] NFS using CacheFS
Date: Wed, 13 Oct 2004 11:40:22 +0100	[thread overview]
Message-ID: <30245.1097664022@redhat.com> (raw)
In-Reply-To: <1097508639.20033.12.camel@lade.trondhjem.org>


Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> That said, David & co.: why did you choose not to use something similar
> to the Solaris syntax for cachefs?

Well...

  (1) when I wrote cachefs I didn't know that Solaris had such a thing

  (2) I don't know what Solaris syntax is - I've seen one example, and that
      didn't make a lot of sense

  (3) my way doesn't involve any changes to userspace programs such as mount

> The "layered filesystem" syntax has the advantage that it would avoid
> entirely the need to change the NFS mount syntax,

And the disadvantage that we'd have to change the VFS to support it, I
think. I don't know how this "layered filesystem" thing operates or is used,
so I'm guessing.

> and would make it easier to port cachefs to cifs etc.

I doubt it. The netfs still has to interact with fscache internally to decide
how match netfs files to cache files, which is what most of the interface is
about; and to push/pull pages to/from the cache (this bit could possibly be
made transparent, but I'm not sure how you'd do it on Linux with the present
VM & VFS interfaces).

David

--
Linux-cachefs mailing list
Linux-cachefs@redhat.com
http://www.redhat.com/mailman/listinfo/linux-cachefs

      parent reply	other threads:[~2004-10-13 10:40 UTC|newest]

Thread overview: 11+ 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-05 10:01   ` David Howells
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-11 14:23     ` Martin Waitz
2004-10-11 15:18       ` David Howells
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         ` 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=30245.1097664022@redhat.com \
    --to=dhowells@redhat.com \
    --cc=SteveD@redhat.com \
    --cc=cs@tequila.co.jp \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=tali@admingilde.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