The problem which this patch wants to solve can be reproduced via ovs 2.16:
1. add a port with an invalid speed parameter: ovs-vsctl add-port ovs-br0 virtiouser0 -- set Interface virtiouser0 type=dpdk options:dpdk-devargs=virtio_user0,path=/dev/vhost-net,queue_size=1024,queues=1,speed=1000 2. delete the failed virtiouser0 port: ovs-vsctl del-port virtiouser0 3. add a new port with valid parameters: ovs-vsctl add-port ovs-br0 virtiouser0 -- set Interface virtiouser0 type=dpdk options:dpdk-devargs=virtio_user0,path=/dev/vhost-net,queue_size=1024,queues=1 The newly added port is always failed because of an existing memory event error.
