From: Martin Waitz <tali@admingilde.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: Clemens Schwaighofer <cs@tequila.co.jp>,
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: Mon, 11 Oct 2004 16:23:29 +0200 [thread overview]
Message-ID: <20041011142329.GJ4072@admingilde.org> (raw)
In-Reply-To: <41667865.2000804@RedHat.com>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
hi :)
On Fri, Oct 08, 2004 at 07:22:13AM -0400, Steve Dickson wrote:
> The 'fscache' flag will be coming along with the nfs4 support, since
> nfs4 mounting code does not have an open (unused) mounting flag....
is such a flag even neccessary?
The way I see fscache is that its operations will be no-ops anyway if you
haven't mounted any backing cache.
--
Martin Waitz
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Martin Waitz <tali@admingilde.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: Linux filesystem caching discussion list
<linux-cachefs@redhat.com>,
nfs@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>,
Clemens Schwaighofer <cs@tequila.co.jp>
Subject: Re: [PATCH] NFS using CacheFS
Date: Mon, 11 Oct 2004 16:23:29 +0200 [thread overview]
Message-ID: <20041011142329.GJ4072@admingilde.org> (raw)
In-Reply-To: <41667865.2000804@RedHat.com>
[-- Attachment #1.1: Type: text/plain, Size: 383 bytes --]
hi :)
On Fri, Oct 08, 2004 at 07:22:13AM -0400, Steve Dickson wrote:
> The 'fscache' flag will be coming along with the nfs4 support, since
> nfs4 mounting code does not have an open (unused) mounting flag....
is such a flag even neccessary?
The way I see fscache is that its operations will be no-ops anyway if you
haven't mounted any backing cache.
--
Martin Waitz
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 108 bytes --]
--
Linux-cachefs mailing list
Linux-cachefs@redhat.com
http://www.redhat.com/mailman/listinfo/linux-cachefs
next prev parent reply other threads:[~2004-10-11 14:30 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
2004-10-08 11:22 ` Steve Dickson
2004-10-08 15:39 ` Clemens Schwaighofer
2004-10-11 14:23 ` Martin Waitz [this message]
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=20041011142329.GJ4072@admingilde.org \
--to=tali@admingilde.org \
--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 \
/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.