Le 02/03/2017 à 01:20, Allain Legacy a écrit :
+Since the initial implementation of AVP devices, vhost-user has become
+part of the qemu offering with a significant performance increase over
+the original virtio implementation. However, vhost-user still does
+not achieve the level of performance that the AVP device can provide
+to our customers for DPDK based VM instances.
Allain,
please, can you be more explicit: why is virtio not fast enough?
Moreover, why should we get another PMD for Qemu/kvm which is not
virtio? There is not argument into your doc about it.
NEC, before vhost-user, made a memnic proposal too because
virtio/vhost-user was not available.
Now, we all agree that vhost-user is the right way to support VMs, it
avoids duplication of maintenances.
Please add some arguments that explains why virtio should not be used,
so others like memnic or avp should be.
Regarding,
+ nova boot --flavor small --image my-image \
+ --nic net-id=${NETWORK1_UUID} \
+ --nic net-id=${NETWORK2_UUID},vif-model=avp \
+ --nic net-id=${NETWORK3_UUID},vif-model=avp \
+ --security-group default my-instance1
I do not see how to get it working with vanilla nova. Please, I think
you should rather show with qemu or virsh.
Then, there is not such AVP netdevice into Linux kernel upstream. Before
adding any AVP support, it should be added into legacy upstream so we
can be sure that the APIs will be solid and won't need to be updated
because of some kernel constraints.
Thank you,
Vincent
