diff options
author | Eric Blake <eblake@redhat.com> | 2019-08-23 09:37:24 -0500 |
---|---|---|
committer | Eric Blake <eblake@redhat.com> | 2019-09-05 16:03:26 -0500 |
commit | f061656cc355161f9984237298c45762ce5187d3 (patch) | |
tree | 7d240be86555e9b9cb558af1e7442febed69a424 /nbd | |
parent | 0a4795455ceeebdca999a60583dd42434f2ec0d1 (diff) | |
download | qemu-f061656cc355161f9984237298c45762ce5187d3.zip |
nbd: Implement client use of NBD FAST_ZERO
The client side is fairly straightforward: if the server advertised
fast zero support, then we can map that to BDRV_REQ_NO_FALLBACK
support. A server that advertises FAST_ZERO but not WRITE_ZEROES
is technically broken, but we can ignore that situation as it does
not change our behavior.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20190823143726.27062-4-eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Diffstat (limited to 'nbd')
0 files changed, 0 insertions, 0 deletions