All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Clemens Schwaighofer <cs@tequila.co.jp>
Cc: 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: Fri, 08 Oct 2004 07:22:13 -0400	[thread overview]
Message-ID: <41667865.2000804@RedHat.com> (raw)
In-Reply-To: <41661950.5070508@tequila.co.jp>

Clemens Schwaighofer wrote:

> brr :) why is it posix, this is so out of the context for me (as a
> user). Is it possible to have a cachefs flag. Would make it more logical.

Because it was the easiest way to get things started (i.e. no userlevel
changes needed at all).... The 'fscache' flag will be coming along with
the nfs4 support, since nfs4 mounting code does not have an open
(unused) mounting flag....

SteveD.

  reply	other threads:[~2004-10-08 11:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 20:45 [PATCH] NFS using CacheFS Steve Dickson
2004-10-04 20:45 ` Steve Dickson
2004-10-04 21:53 ` Trond Myklebust
2004-10-04 21:53   ` Trond Myklebust
2004-10-05 10:01 ` David Howells
2004-10-05 10:01   ` David Howells
2004-10-08  4:36 ` Clemens Schwaighofer
2004-10-08  4:36   ` Clemens Schwaighofer
2004-10-08 11:22   ` Steve Dickson [this message]
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: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       ` [Linux-cachefs] Re: [PATCH] NFS using CacheFS David Howells
2004-10-13 10:40         ` David Howells
2004-10-11 15:18     ` [Linux-cachefs] " David Howells
2004-10-11 15:18       ` David Howells
2004-10-08  9:02 ` [Linux-cachefs] " David Howells
2004-10-08  9:02   ` 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=41667865.2000804@RedHat.com \
    --to=steved@redhat.com \
    --cc=cs@tequila.co.jp \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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.