Description of problem: ovs-dpdk bond type "balance-tcp" is currently not support for production environment.It degrades the performance due to extra re-circulations in the datapath. However, "other_config:lb-output-action=true" helps to improve performance with balance-tcp bond. we can set it as below. Default is false. ovs-vsctl set port <bond port> other_config:lb-output-action=<true|false> We can verify configuration with below ovs-appctl dpif-netdev/dp-bond-show [dp] ovs-appctl bond/show Currently we configure ovs-dpdk bond via ovs_extra in tripleO. we shall continue same with lb-output-action flag set. - type: ovs_user_bridge name: br-link0 use_dhcp: false ovs_extra: - str_replace: template: set port br-link0 tag=_VLAN_TAG_ params: _VLAN_TAG_: get_param: TenantNetworkVlanID addresses: - ip_netmask: get_param: TenantIpSubnet members: - type: ovs_dpdk_bond name: dpdkbond0 mtu: 9000 rx_queue: 1 ovs_extra: - set port dpdkbond0 bond_mode=balance-slb members: - type: ovs_dpdk_port name: dpdk0 members: - type: interface name: nic7 - type: ovs_dpdk_port name: dpdk1 members: - type: interface name: nic8 lb-output-action is already supported by red hat fast datapath. Expectations here are - Successful deployment on all nodes with lb-output-action - Performance comparison with/without lb-output-action Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: