On Thu, Mar 17, 2016 at 3:43 PM, Chandran, Sugesh <sugesh.chand...@intel.com> wrote: > Hi, > > This patch proposes an approach that uses Flow director feature on the Intel > Fortville NICs to boost the VxLAN tunneling performance. In our testing we > verified that the VxLAN performance is almost doubled with this patch. > The solution programs the NIC to report the flow ID along with the VxLAN > packets, and it is matched by OVS in software. There may be corner cases that > needs to addressed in the approach, For eg: There is a possibility of race > condition where NIC reports flow ID that may match on different flow in OVS. > This happen when a rule is evicted by a new rule with same flowID+ hash in > the OVS software. The packets may hit on wrong new rule in OVS until the flow > get deleted in the hardware too. > > It is a hardware specific implementation (Only work with Intel Fortville > NICs) for now, however the proposal works with any programmable NICs.This RFC > proves that the OVS can offer very high speed tunneling performance using > flow programmability in NICs. I am looking for comments/suggestions on adding > this support(such as configuring, enable it for all the programmable NICs and > etc) in OVS userspace datapath for improving the performance.
This is definitely very interesting to see. Can you post some more specific performance numbers? Is this really specific to VXLAN? I'm sure that it could be generalized to other tunneling protocols (Geneve would be nice given that OVN is using it and I know Fortville supports it). But shouldn't it apply to non-tunneled traffic as well? It looks like this is adding a hardware flow when a new flow is added to the datapath. How does this affect flow setup performance? Otherwise, I agree that it will be important to generalize this for the final version. The obvious things that I noticed were supporting different types of NICs, using the configured tunnel UDP port(s) rather than a hardcoded one, and integrating the code so that #ifdefs aren't necessary. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
