summary refs log tree commit diff stats
path: root/include/hw/acpi/acpi_dev_interface.h
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2016-10-14 13:33:18 -0500
committerPaolo Bonzini <pbonzini@redhat.com>2016-11-02 09:28:56 +0100
commitfa778fffdfafce811bba3dd97de41fb524b861f7 (patch)
tree9e44cd06de20db032f56d0aec6ce432318e126a8 /include/hw/acpi/acpi_dev_interface.h
parent1f4d6d18edfeaea64ae74bf5254b8d0e923dc73f (diff)
downloadfocaccia-qemu-fa778fffdfafce811bba3dd97de41fb524b861f7.tar.gz
focaccia-qemu-fa778fffdfafce811bba3dd97de41fb524b861f7.zip
nbd: Implement NBD_CMD_WRITE_ZEROES on client
Upstream NBD protocol recently added the ability to efficiently
write zeroes without having to send the zeroes over the wire,
along with a flag to control whether the client wants a hole.

The generic block code takes care of falling back to the obvious
write of lots of zeroes if we return -ENOTSUP because the server
does not have WRITE_ZEROES.

Ideally, since NBD_CMD_WRITE_ZEROES does not involve any data
over the wire, we want to support transactions that are much
larger than the normal 32M limit imposed on NBD_CMD_WRITE.  But
the server may still have a limit smaller than UINT_MAX, so
until experimental NBD protocol additions for advertising various
command sizes is finalized (see [1], [2]), for now we just stick to
the same limits as normal writes.

[1] https://github.com/yoe/nbd/blob/extension-info/doc/proto.md
[2] https://sourceforge.net/p/nbd/mailman/message/35081223/

Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1476469998-28592-17-git-send-email-eblake@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'include/hw/acpi/acpi_dev_interface.h')
0 files changed, 0 insertions, 0 deletions