First of all I would update to OVS 2.4 or master.
That said, the first issue you're facing might be related to a
packet leak (I suspect in the code that moves the packets to the
slow path). You could check the hit/miss counters with
`ovs-appctl dpif/show` (we added ovs-appctl dpif-netdev/pmd-stats
Hi Daniele,
I have a way to mitigate the problem by stopping rte_eth_rx_burst until
all the rules have settled. I do this with an options: argument in
other_config (amongst other arguments using this free form field - like
dedup and defrag features i am experimenting with) My rules are static so
Hi Daniele!
Thank you for your reply.
I find that it reliably starts too if i have 6 or less NIC ports.
Any more than 6 ports (even if there is only one receiving traffic) and the
one receivng traffic will just keep upping the rx_errors.
Ovs is automatically adding 11pmd's because i have a FFF ma
I regularly start ovs with dpdk while traffic is flowing.
Is there anything suspicious in the ovs-vswitchd log?
Have you tried other DPDK apps (e.g. l2fwd)?
On 25/09/2015 17:28, "David Evans" wrote:
>Hi all,
>
>
>Has anyone seen that when starting ovs (with dpdk) that the port will
>show many
Hi all,
Has anyone seen that when starting ovs (with dpdk) that the port will show
many rx-errors and the device will stop receiving traffic?
Is there a mitigation for this.
I have tried adding drop all flows to the bridge before all my other flows
are set up.
I have tried disabling the port rx to
