Docs: Remove zero-copy QEMU limitation.

Remove note regarding zero-copy compatibility with QEMU >= 2.7. When zero-copy was introduced to OVS it was incompatible with QEMU >= 2.7. This issue has since been fixed in DPDK with commit 803aeec ("vhost: fix dequeue zero copy with virtio1") and backported to DPDK LTS branches. Remove the reference to this issue in the zero-copy documentation. Cc: Ciara Loftus <[email protected]> Acked-by: Ciara Loftus <[email protected]> Signed-off-by: Ian Stokes <[email protected]>
timofei-durakov · Nov 2, 2018 · 8b7baf5 · 8b7baf5
1 parent 9474073
commit 8b7baf5
Showing 1 changed file with 0 additions and 6 deletions.
diff --git a/Documentation/topics/dpdk/vhost-user.rst b/Documentation/topics/dpdk/vhost-user.rst
@@ -500,12 +500,6 @@ QEMU versions v2.10 and greater). This value can be set like so::
 
 Because of this limitation, this feature is considered 'experimental'.
 
-The feature currently does not fully work with QEMU >= v2.7 due to a bug in
-DPDK which will be addressed in an upcoming release. The patch to fix this
-issue can be found on
-`Patchwork
-<http://dpdk.org/dev/patchwork/patch/32198/>`__
-
 Further information can be found in the
 `DPDK documentation
 <http://dpdk.readthedocs.io/en/v17.11/prog_guide/vhost_lib.html>`__