Re: [dpdk-dev] [PATCH v3 0/4] Vhost: fix mq=on but VIRTIO_NET_F_MQ not negotiated

2017-12-06 Thread Ladi Prosek
On Wed, Dec 6, 2017 at 10:20 AM, Maxime Coquelin wrote: > Hi, > > This third revision reworks the VQs destruction loop to fixes the > of-by-one error reported by Laszlo. > > Having QEMU started with mq=on but guest driver not negotiating > VIRTIO_NET_F_MQ feature ends up in the vhost device to nev

Re: [dpdk-dev] [PATCH v3 0/4] Vhost: fix mq=on but VIRTIO_NET_F_MQ not negotiated

2017-12-06 Thread Laszlo Ersek
On 12/06/17 10:20, Maxime Coquelin wrote: > Hi, > > This third revision reworks the VQs destruction loop to fixes the > of-by-one error reported by Laszlo. > > Having QEMU started with mq=on but guest driver not negotiating > VIRTIO_NET_F_MQ feature ends up in the vhost device to never > start. I

[dpdk-dev] [PATCH v3 0/4] Vhost: fix mq=on but VIRTIO_NET_F_MQ not negotiated

2017-12-06 Thread Maxime Coquelin
Hi, This third revision reworks the VQs destruction loop to fixes the of-by-one error reported by Laszlo. Having QEMU started with mq=on but guest driver not negotiating VIRTIO_NET_F_MQ feature ends up in the vhost device to never start. Indeed, more queues are created in the vhost backend than c