linux-kernel - Re: [fuse-devel] [PATCHSET] CUSE: implement CUSE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080901073844.GA5376@glandium.org>
Date:	Mon, 1 Sep 2008 09:38:45 +0200
From:	Mike Hommey <mh@...ndium.org>
To:	Goswin von Brederlow <goswin-v-b@....de>
Cc:	Tejun Heo <tj@...nel.org>, fuse-devel@...ts.sourceforge.net,
	greg@...ah.com, linux-kernel@...r.kernel.org, miklos@...redi.hu
Subject: Re: [fuse-devel] [PATCHSET] CUSE: implement CUSE

On Mon, Sep 01, 2008 at 09:20:19AM +0200, Goswin von Brederlow <goswin-v-b@....de> wrote:
> Mike Hommey <mh@...ndium.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.

That already exists. http://wiki.xensource.com/xenwiki/DmUserspace

Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/