On 20 Aug 2015, at 15:43, Markus Pargmann <[email protected]> wrote:
> > it seems qemu-nbd has a complete separate implementation of NBD. Does > anyone know what the state of qemu-nbd and its differences to > nbd-server/client is? > > I am wondering why there is a second implementation. Wouldn't it be > better to have a single implementation with more test coverage and > contributions? On the server side, qemu-nbd and friends are built around some quite complex coroutine stuff unique to qemu, and use an interesting backend that supports various on disk file formats (qcow etc.) nbd-server itself is much simpler. In terms of the client code, qemu's is userland, nbd's is mostly kernel side. I think it's thus not going to be practical to merge them (but qemu-devel is where you'd need to ask). Actually, having two interoperating implementations is a *good* thing as far as maintaining a standard is concerned. -- Alex Bligh
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------
_______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
