public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Alexander Viro <viro@math.psu.edu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de>,
	Jonathan Barker <jbarker@ebi.ac.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: VFS mediator?
Date: Mon, 18 Mar 2002 20:25:02 +0100	[thread overview]
Message-ID: <20020318192502.GD194@elf.ucw.cz> (raw)
In-Reply-To: <E16lej0-0002FE-00@the-village.bc.nu> <Pine.GSO.4.21.0203141825070.329-100000@weyl.math.psu.edu>

Hi!

> > > I have experimented with using NFS for that -- start a local daemon that
> > > exports a virtual filesystem and mount that. The great bonus is that it's
> > > platform independent -- it works on Solaris, HP-UX and even Ultrix just as
> > > well. Other projects have become more important, however, and I haven't
> > > finished it. If you're interested, drop me a line.
> > 
> > There are several of these and also some folks using the coda interface
> > to do the same work, as the coda interface is sometimes better suited. 
> 
> ... for some kinds of work.
> 
> First of all, "VFS mediator" is simply a userland filesystem.  That's
> precisely what it is - filesystem that talks to a process.  We've got
> quite a few of them and which one fits the task depends on the task.
> 
> 	* NFS (v2,v3):  Portable.  And that's the only good thing to say
> about it - it's stateless, it has messy semantics all over the place and
> implementing userland server requires a lot of glue.

Does not work... If you mount nfs server on localhost, you can deadlock.

> 	* CODA: nice if you want commit-on-close semantics and basically
> want a lot of regular files.  More or less portable, userland side doesn't
> require much glue.  Has a nice local caching and as the result bad for any
> RPC-style uses.

And the only one that works when r/w mounted on localhost.
									Pavel
-- 
(about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa

  parent reply	other threads:[~2002-03-18 19:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 14:52 VFS mediator? Jonathan Barker
2002-03-14 23:09 ` Simon Richter
2002-03-14 23:33   ` Alan Cox
2002-03-15  0:00     ` Alexander Viro
2002-03-15 11:50       ` Simon Richter
2002-03-18 19:25       ` Pavel Machek [this message]
2002-03-18 22:18         ` Trond Myklebust
2002-03-18 22:38           ` Pavel Machek
2002-03-18 22:48             ` Trond Myklebust
2002-03-18 22:54               ` Pavel Machek
2002-03-18 23:05                 ` Trond Myklebust
2002-03-19  0:15           ` Alan Cox
2002-03-18 22:29         ` Alexander Viro
2002-03-18 22:36           ` Pavel Machek
2002-03-15 14:28 ` Jonathan Barker
  -- strict thread matches above, loose matches on Subject: below --
2002-03-19 13:45 Jesse Pollard
2002-03-19 21:24 ` Pavel Machek

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=20020318192502.GD194@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=Simon.Richter@phobos.fachschaften.tu-muenchen.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jbarker@ebi.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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