The current OVS-DPDK implementation doesnt allow users to run another DPDK application simultaneously on the same platform.
To avoid this limitation, the patch series offers two configuration options to isolate the OVS-DPDK process completely on a platform. 1) The configuration option is added to isolate the DPDK memory allocation in need. This option allocate and use a seperate DPDK memory pool region for OVS, instead of standard DPDK memory pool. 2) Configuration option to whitelist the ports that are going to use in OVS. This option causes DPDK to init only specific ports and its drivers at the time of vswitchd init. Sugesh Chandran (2): Adding DPDK configuration option to isolate rte-mempool allocation. Adding configuration option to whitelist DPDK physical ports. lib/daemon.c | 9 ++++++++ lib/daemon.h | 1 + lib/dpdk.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++ vswitchd/vswitch.xml | 44 ++++++++++++++++++++++++++++++++++++ 4 files changed, 117 insertions(+) -- 2.7.4 _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev