aboutsummaryrefslogtreecommitdiff
path: root/block
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2016-10-14 13:33:17 -0500
committerPaolo Bonzini <pbonzini@redhat.com>2016-11-02 09:28:56 +0100
commit1f4d6d18edfeaea64ae74bf5254b8d0e923dc73f (patch)
treea8cd9fbf92b2639ac0749a72a5702d0ecdb90d11 /block
parentb6f5d3b573fe43da1f9fa07b7454e4492f409411 (diff)
downloadqemu-1f4d6d18edfeaea64ae74bf5254b8d0e923dc73f.zip
qemu-1f4d6d18edfeaea64ae74bf5254b8d0e923dc73f.tar.gz
qemu-1f4d6d18edfeaea64ae74bf5254b8d0e923dc73f.tar.bz2
nbd: Implement NBD_CMD_WRITE_ZEROES on server
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 to allow a hole. Note that when it comes to requiring full allocation, vs. permitting optimizations, the NBD spec intentionally picked a different sense for the flag; the rules in qemu are: MAY_UNMAP == 0: must write zeroes MAY_UNMAP == 1: may use holes if reads will see zeroes while in NBD, the rules are: FLAG_NO_HOLE == 1: must write zeroes FLAG_NO_HOLE == 0: may use holes if reads will see zeroes In all cases, the 'may use holes' scenario is optional (the server need not use a hole, and must not use a hole if subsequent reads would not see zeroes). Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <1476469998-28592-16-git-send-email-eblake@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions