The following upstream commits mitigate this issue by allowing the user to control tx queue size (up to 1024). When this is done, the performance drop caused by the commit, showed in the previous comment, is mitigated.
# QEMU commit 9b02e1618cf26aa52cf786f215d757506dda14f8 Author: Wei Wang <[email protected]> Date: Wed Jun 28 10:37:59 2017 +0800 virtio-net: enable configurable tx queue size commit 2eef278b9e6326707410eed23be40e57f6c331b7 Author: Michael S. Tsirkin <[email protected]> Date: Mon Jul 3 22:25:24 2017 +0300 virtio-net: fix tx queue size for !vhost-user # LIBVIRT commit 2074ef6cd4a2e033813ec091487d027a85f73509 Author: Michal Privoznik <[email protected]> Date: Wed Jul 12 14:19:26 2017 +0200 Add support for virtio-net.tx_queue_size # NOVA COMPUTE (pending, not yet accepted) https://blueprints.launchpad.net/nova/+spec/libvirt-virtio-set-queue- sizes https://review.openstack.org/#/c/484997/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668829 Title: Performance regression from qemu 2.3 to 2.5 for vhost-user with ovs + dpdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1668829/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
