From: Goswin von Brederlow <goswin-v-b@web.de>
To: Mike Hommey <mh@glandium.org>
Cc: Tejun Heo <tj@kernel.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: Mon, 01 Sep 2008 09:20:19 +0200 [thread overview]
Message-ID: <87iqtggwng.fsf@frosties.localdomain> (raw)
In-Reply-To: <20080830185613.GC12546@glandium.org> (Mike Hommey's message of "Sat, 30 Aug 2008 20:56:13 +0200")
Mike Hommey <mh@glandium.org> writes:
> On Sat, Aug 30, 2008 at 02:30:32PM +0200, Tejun Heo wrote:
>> Yeah, compared to loopback over FUSE, anything would have less
>> problem. :-) I don't know much about nbd but it's pretty much solving
>> the same problem so I think it's logical to extend nbd including
>> giving it a new transport if necessary? Or is there something
>> fundamentally better when it's done via FUSE?
>
> My gutt feeling is that it would have less overhead when done via FUSE
> than through nbd, but that could be wrong.
>
> Mike
What I would hope is that BUSE would add some zero copy transport in
there. A way to just redirect the BIOs from the BUSE device to other
block devices without copying the data around.
But maybe BUSE is a bad name for that. That would be more a DUSE -
Device mapper in USEr space.
MfG
Goswin.
next prev parent reply other threads:[~2008-09-01 7:20 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
2008-08-30 12:30 ` Tejun Heo
2008-08-30 18:56 ` Mike Hommey
2008-09-01 7:20 ` Goswin von Brederlow [this message]
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=87iqtggwng.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--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®