Messages in this thread | | | From | Goswin von Brederlow <> | Subject | Re: [fuse-devel] [PATCHSET] CUSE: implement CUSE | Date | Mon, 01 Sep 2008 09:20:19 +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.
| |