Releases: everoute/ovs
Releases · everoute/ovs
release-3.3.4
dpif: pass portnames of ofproto to kernel datapath When an RDMA capable device is linked to OVS bridge, and if we want to run RoCE over the device, the internal port of the OVS bridge should be set as the upper device of the RDMA capable device, so that kernel will add RDMA GIDs for the internal port and we can use them for RoCE communication. The userspace ovs-vswitchd will pass the portnames of a ofproto to the kernel openvswitch module via netlink when creating a vport, and kernel side will parse the portnames and setup adjacent devices for the vport's netdev properly.
release-3.3.3
dpif: pass portnames of ofproto to kernel datapath When an RDMA capable device is linked to OVS bridge, and if we want to run RoCE over the device, the internal port of the OVS bridge should be set as the upper device of the RDMA capable device, so that kernel will add RDMA GIDs for the internal port and we can use them for RoCE communication. The userspace ovs-vswitchd will pass the portnames of a ofproto to the kernel openvswitch module via netlink when creating a vport, and kernel side will parse the portnames and setup adjacent devices for the vport's netdev properly.