/test/scapy_handlers/

alternate' title='Atom feed' href='http://git.fd.io/vpp/atom/docs/usecases/vhost/vhost05.rst?h=v19.01.3' type='application/atom+xml'/>
summaryrefslogtreecommitdiffstats
path: root/docs/usecases/vhost/vhost05.rst
blob: 4eba6e171010286975c4454951a868f31fdc5610 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
.. _vhost05:

Limitations
-----------
There are some limitations when using the qemu vhost driver. Some are described in this section.

Performance
^^^^^^^^^^^

VPP performance with vHost is limited by the Qemu vHost driver. FD.io VPP 18.04 CSIT vHost testing
shows with 2 threads, 2 cores and a Queue size of 1024 the maximum NDR throughput was about 7.5 Mpps.
This is about the limit at this time.

For all the details on the CSIT VM vhost connection refer to the 
`CSIT VM vHost performance tests <https://docs.fd.io/csit/rls1804/report/vpp_performance_tests/packet_throughput_graphs/vm_vhost.html>`_.


Features
^^^^^^^^

These are the features not supported with FD.io VPP vHost.

* VPP implements vHost in device mode only. VPP is intended to work with Qemu which implements vHost in driver mode, it does not implement vHost driver mode.
* VPP vHost implementation does not support checksum or transmit segmentation offload.
* VPP vHost implementation does not support packet receive filtering feature for controlling receive traffic.