mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Archie Cobbs" <archie@dellroad.org>
To: "Tejun Heo" <tj@kernel.org>
Cc: "Mike Hommey" <mh@glandium.org>,
	fuse-devel@lists.sourceforge.net, greg@kroah.com,
	linux-kernel@vger.kernel.org, miklos@szeredi.hu
Subject: Re: [fuse-devel] [PATCHSET] CUSE: implement CUSE
Date: Fri, 29 Aug 2008 13:50:21 -0500	[thread overview]
Message-ID: <3bc8237c0808291150t2f18ba64vf445bdf4c2c8360c@mail.gmail.com> (raw)
In-Reply-To: <48B78EBA.609@kernel.org>

On Fri, Aug 29, 2008 at 12:52 AM, Tejun Heo <tj@kernel.org> wrote:
> Mike Hommey wrote:
> > On Fri, Aug 29, 2008 at 03:18:59AM +0900, Tejun Heo wrote:
> >> This patchset implements CUSE - Character device in Userspace.  Except
> >> for initialization sequence and creation of character device instead
> >> of a mount, CUSE isn't very different from FUSE.
> >
> > It would be nice to have BUSE, Block device in Userspace, too.
>
> Thought about that but it's really no different from nbd or loop
> depending on your application and block devices don't really implement
> the file operations so it won't have too much in common with FUSE.

I think BUSE would be useful. For one, it allows you to avoid problems with
the extra caching you get with a loopback device. And NBD is too limiting
for some applications.

For my half-ignorant analysis of the caching issues, see:
  http://code.google.com/p/s3backer/wiki/PerformanceConsiderations#Caching

This is also an example of an application where NBD doesn't suffice.

> Also, there's the complication of going out to disk for more memory cases.

Not sure what you mean exactly (my fault), but it seems BUSE would have fewer
places for memory problems (including deadlocks) than loopback over FUSE,
which is the only way to do this kind of stuff now.

-Archie

--
Archie L. Cobbs

  reply	other threads:[~2008-08-29 18:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 18:18 Tejun Heo
2008-08-28 18:19 ` [PATCH 1/5] FUSE: add fuse_ prefix to several functions Tejun Heo
2008-08-28 18:19 ` [PATCH 2/5] FUSE: export symbols to be used by CUSE Tejun Heo
2008-08-28 18:19 ` [PATCH 3/5] FUSE: separate out fuse_conn_init() from new_conn() Tejun Heo
2008-08-28 18:19 ` [PATCH 4/5] FUSE: add fuse_conn->release() Tejun Heo
2008-08-28 18:19 ` [PATCH 5/5] CUSE: implement CUSE - Character device in Userspace Tejun Heo
2008-08-28 20:07   ` Andrew Morton
2008-08-28 22:15     ` Greg KH
2008-08-28 22:32       ` Andrew Morton
2008-08-29  2:09     ` Tejun Heo
2008-08-29  2:20       ` Andrew Morton
2008-08-29 15:27       ` Nick Bowler
2008-08-29  5:50 ` [fuse-devel] [PATCHSET] CUSE: implement CUSE Mike Hommey
2008-08-29  5:52   ` Tejun Heo
2008-08-29 18:50     ` Archie Cobbs [this message]
2008-08-30 12:30       ` Tejun Heo
2008-08-30 18:56         ` Mike Hommey
2008-09-01  7:20           ` Goswin von Brederlow
2008-09-01  7:38             ` Mike Hommey
2008-08-30 22:39         ` Archie Cobbs
2008-08-31  4:52   ` hooanon05
2008-08-30 16:35 ` Goswin von Brederlow

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=3bc8237c0808291150t2f18ba64vf445bdf4c2c8360c@mail.gmail.com \
    --to=archie@dellroad.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mh@glandium.org \
    --cc=miklos@szeredi.hu \
    --cc=tj@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

all inboxes | Powered by JetHome®