Thanks for working on this. That was on my backlog to try out for a while.
One immediate feedback: This is a pure OVS user space patch. Please remove the
"net-next" tag from your patches in the next version. "net-next" is reserved
for OVS kernel module patches that are first submitted upstream to the Linux
> -----Original Message-----
> From: ovs-dev-boun...@openvswitch.org
> [mailto:ovs-dev-boun...@openvswitch.org] On Behalf Of xiangxia.m....@gmail.com
> Sent: Thursday, 12 April, 2018 14:53
> To: d...@openvswitch.org
> Subject: [ovs-dev] [PATCH net-next 0/6] Add dpdk-bond support
> From: Tonghao Zhang <xiangxia.m....@gmail.com>
> The bond of openvswitch has not good performance. In some
> cases we would recommend that you use Linux bonds instead
> of Open vSwitch bonds. In userspace datapath, we wants use
> bond to improve bandwidth. The DPDK has implemented it as lib.
> These patches base DPDK bond to implement the dpdk-bond
> device as a vswitchd interface.
> If users set the interface options with multi-pci or device names
> with ',' as a separator, we try to parse it as dpdk-bond args.
> For example, set an interface as:
> ovs-vsctl add-port br0 dpdk0 -- \
> set Interface dpdk0 type=dpdk \
> And now these patch support to set bond mode, such as round
> robin, active_backup and balance and so on. Later some features
> of bond will be supported.
> These patches are RFC, any proposal will be welcome. Ignore the doc,
> if these pathes is ok for openvswitch the doc will be posted.
> There are somes shell scripts, which can help us to test the patches.
> Tonghao Zhang (6):
> netdev-dpdk: Allow vswitchd to parse devargs as dpdk-bond args
> netdev-dpdk: Allow dpdk-ethdev not support setting mtu
> netdev-dpdk: Add netdev_dpdk_bond struct
> netdev-dpdk: Add dpdk-bond support
> netdev-dpdk: Add check whether dpdk-port is used
> netdev-dpdk: Add dpdk-bond mode setting
> lib/netdev-dpdk.c | 304
> 1 file changed, 299 insertions(+), 5 deletions(-)
> dev mailing list
dev mailing list