public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Britt Park <britt@drscience.sciencething.org>,
	Miklos.Szeredi@eth.ericsson.se
Cc: linux-kernel@vger.kernel.org
Subject: Re: UVFS Yet another user space filesystem kit.
Date: Thu, 24 Jan 2002 23:12:05 +0100	[thread overview]
Message-ID: <20020124221204.GA906@elf.ucw.cz> (raw)
In-Reply-To: <B871843F.200D%britt@sciencething.org>
In-Reply-To: <B871843F.200D%britt@sciencething.org>

Hi!

> I would like to announce the availability of version 0.1 of UVFS, yet
> another user space filesystem kit.  UVFS provide an interface to almost all
> kernel VFS methods in user space with acceptable overhead.  It comes with a
> sample in memory filesystem as documentation.
> 
> As far as I can determine UVFS is quite robust but I would love to have some
> independent confirmation of that.  I would also be delighted if someone more
> familiar with the linux VFS than I, were to give the code a once-over.
> 
> The current version of UVFS only supports a single instance of a given
> filesystem type.  That will be addressed in the next public release.
> 
> UVFS can be found at http://www.sciencething.org/geekthings/index.html .

How do you solve deadlocks on writing?

[Imagine so many dirty buffers are in memory that your
filesystem-in-userspace-daemon was swapped out?]

[Miklos, Cc-ed to you. You have that problem too. And it probably has
same solution like those untrusted filesystems -- back it up by a file.]
									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

      reply	other threads:[~2002-01-25 23:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 16:39 UVFS Yet another user space filesystem kit Britt Park
2002-01-24 22:12 ` Pavel Machek [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=20020124221204.GA906@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=Miklos.Szeredi@eth.ericsson.se \
    --cc=britt@drscience.sciencething.org \
    --cc=linux-kernel@vger.kernel.org \
    /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