[dpdk-dev] [PATCH] doc: note a pitfall on reconnect feature

2016-07-22 Thread Thomas Monjalon
2016-07-20 09:08, Yuanhan Liu: > On Tue, Jul 19, 2016 at 01:57:11PM +, Mcnamara, John wrote: > > > - Note: the "reconnect" feature requires **QEMU v2.7** (or above). > > > + .. Note:: > > > + * The "reconnect" feature requires **QEMU v2.7** (or above). > > > + > > > + * The vhost supp

[dpdk-dev] [PATCH] doc: note a pitfall on reconnect feature

2016-07-20 Thread Yuanhan Liu
On Tue, Jul 19, 2016 at 01:57:11PM +, Mcnamara, John wrote: > > - Note: the "reconnect" feature requires **QEMU v2.7** (or above). > > + .. Note:: > > + * The "reconnect" feature requires **QEMU v2.7** (or above). > > + > > + * The vhost supported features must be exactly the same bef

[dpdk-dev] [PATCH] doc: note a pitfall on reconnect feature

2016-07-19 Thread Mcnamara, John
> - Note: the "reconnect" feature requires **QEMU v2.7** (or above). > + .. Note:: > + * The "reconnect" feature requires **QEMU v2.7** (or above). > + > + * The vhost supported features must be exactly the same before and > + after the restart. For example, if TSO is disabled and t

[dpdk-dev] [PATCH] doc: note a pitfall on reconnect feature

2016-07-19 Thread Yuanhan Liu
The vhost feature negotiation only happens at virtio reset stage, say when a virtio-net device is firstly initiated, or when DPDK virtio PMD initiates. That means, if vhost APP restarts after the negotiation and reconnects, the feature negotiation process will not be triggered again, meaning the in