Kevin Wolf cd7fca952c nbd-server: Use a separate BlockBackend ... The builtin NBD server uses its own BlockBackend now instead of reusing the monitor/guest device one. This means that it has its own writethrough setting now. The builtin NBD server always uses writeback caching now regardless of whether the guest device has WCE enabled. qemu-nbd respects the cache mode given on the command line. We still need to keep a reference to the monitor BB because we put an eject notifier on it, but we don't use it for any I/O. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com>		2016-09-05 19:06:47 +02:00
..
client.c	nbd: Limit nbdflags to 16 bits	2016-08-03 18:44:56 +02:00
common.c	nbd: Drop unused offset parameter	2016-07-20 14:11:54 +01:00
Makefile.objs	nbd: Split nbd.c	2016-01-15 18:58:02 +01:00
nbd-internal.h	nbd: Drop unused offset parameter	2016-07-20 14:11:54 +01:00
server.c	nbd-server: Use a separate BlockBackend	2016-09-05 19:06:47 +02:00