When I try to set other_config:n-dpdk-rxqs to 64 with two intel niantic dpdk
ports on a single dpdk bridge, the bridge instance will 'crash' - I
can't access
it's flows through ovs-ofctl commands. I am running an OVS from the 2.5
branch,
specifically commit ID b3e263929a7a00c96a1329f93f1b8fce58
Hi. I sent an email the other day about difficulties initializing DPDK
with a certain NIC card. Basically I got bizarre errors when I added a
dpdk port to a bridge using this card (Mellanox CX3Pro) with OVS
2.5+DPDK-16.04 (ovs 2.5 + some commits on branch-2.5, and with a patch
for DPDK 16.04 co
DK is initialized is changed
with releases after 2.5 (currently, nothing released yet). It would be
good to confirm whether your issue is present or not present.
Thanks,
Aaron
John Phillips writes:
Hi. I am testing a build of openvswitch with DPDK that we package for
our debian linux distrib
Hi. I am testing a build of openvswitch with DPDK that we package for
our debian linux distribution called 'openvswitch-switch-dpdk' which is
the normal debian package with the ovs-vswitchd used within the debian
alternatives system (<- not too important). We are trying to support the
intel nia
