linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Jan Kasprzak <kas@informatics.muni.cz>,
	linux-kernel@vger.kernel.org, xgajda@fi.muni.cz, kron@fi.muni.cz
Subject: Re: CacheFS
Date: Sat, 9 Jun 2001 10:29:36 +0200	[thread overview]
Message-ID: <20010609102936.A660@bug.ucw.cz> (raw)
In-Reply-To: <20010607133750.I1193@informatics.muni.cz> <20010607114419.A23962@cs.cmu.edu>
In-Reply-To: <20010607114419.A23962@cs.cmu.edu>; from Jan Harkes on Thu, Jun 07, 2001 at 11:44:19AM -0400

Hi!

> > * Can the kernel part of CODA can be used for this?
> 
> Not if you want to intercept and redirect every single read and write
> call. That's a whole other can of worms, and I'd advise you to let the
> userspace cachemanager to act as an NFS daemon. In my opinion, the Coda
> kernel module fills a specific niche, and should not become yet another
> kernel NFS client implementation that happens to bounce requests to
> userspace using read/write on a character device instead of RPC/UDP
> packets to a socket.

Forget NFS if you want it to be read/write. There are nasty deadlocks
out there.

> AVFS,
>     Another userfs implementation that when from a shared library hack
>     to using the Coda kernel module,
> 
>     http://sourceforge.net/projects/avfs

avfs moved to sourceforge? Wow!
								Pavel
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

  parent reply	other threads:[~2001-06-10 11:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07 11:37 CacheFS Jan Kasprzak
2001-06-07 15:44 ` CacheFS Jan Harkes
2001-06-08 11:48   ` CacheFS Jan Kasprzak
2001-06-09  8:29   ` Pavel Machek [this message]
2001-06-07 22:23 ` CacheFS Albert D. Cahalan
2001-06-08  5:15   ` CacheFS Michael Clark
     [not found] <200603232313.k2NNDEW2006900@shell0.pdx.osdl.net>
2006-03-23 23:20 ` cachefs sv

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=20010609102936.A660@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=kas@informatics.muni.cz \
    --cc=kron@fi.muni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xgajda@fi.muni.cz \
    /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).