[dpdk-dev] [PATCH] vhost: fix driver unregister for client mode

2016-07-21 Thread Yuanhan Liu
On Wed, Jul 20, 2016 at 11:32:43AM +0300, Ilya Maximets wrote: > Currently while calling of 'rte_vhost_driver_unregister()' connection > to QEMU will not be closed. This leads to inability to register driver > again and reconnect to same virtual machine. > > This scenario is reproducible with OVS.

[dpdk-dev] [PATCH] vhost: fix driver unregister for client mode

2016-07-21 Thread Ilya Maximets
Thanks. Fixed. Best regards, Ilya Maximets. On 21.07.2016 11:24, Yuanhan Liu wrote: > On Wed, Jul 20, 2016 at 11:32:43AM +0300, Ilya Maximets wrote: >> Currently while calling of 'rte_vhost_driver_unregister()' connection >> to QEMU will not be closed. This leads to inability to register driver >

[dpdk-dev] [PATCH] vhost: fix driver unregister for client mode

2016-07-20 Thread Yuanhan Liu
On Wed, Jul 20, 2016 at 11:32:43AM +0300, Ilya Maximets wrote: > Currently while calling of 'rte_vhost_driver_unregister()' connection > to QEMU will not be closed. This leads to inability to register driver > again and reconnect to same virtual machine. > > This scenario is reproducible with OVS.

[dpdk-dev] [PATCH] vhost: fix driver unregister for client mode

2016-07-20 Thread Ilya Maximets
Currently while calling of 'rte_vhost_driver_unregister()' connection to QEMU will not be closed. This leads to inability to register driver again and reconnect to same virtual machine. This scenario is reproducible with OVS. While executing of the following command vhost port will be re-created (