Hi Kevin, The performance number looks great! - For DPDK OVS, the number only shows NIC - OVS - NIC as vhost-user is not supported yet, do you know what's the schedule for vhost-user support? - On slide #8, it's interesting to see TCP_STREAM degrade quite a lot in offload case.
Thanks, Jun On Thu, Dec 18, 2014 at 9:32 PM, Traynor, Kevin <kevin.tray...@intel.com> wrote: > Hi John, > > The path using DPDK through the netdev can use the exact match cache in > dpif-netdev.c to enable very fast switching. You could think of this as an > equivalent to the fast path in OVDK. Have a look at the rates that Madhu > Challa presented at the OVS Fall Conference on Slide 3 > http://openvswitch.org/support/ovscon2014/18/1600-ovs_perf.pptx > > Thanks, > Kevin. > >> -----Original Message----- >> From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of John Xiao >> Sent: Wednesday, December 17, 2014 4:10 AM >> To: dev@openvswitch.org >> Subject: [ovs-dev] OVS DPDK support technical direction >> >> Hi, >> >> As we know that Intel stopped its effort on OVDK and OVS DPDK support >> will all be in OVS upstream, and I have one question after digging >> OVDK and OVS DPDK architecture: >> >> - IMHO, OVS DPDK support can follow the existing "fast/slow path" >> model as being done in OVS linux kernel, i.e. just another fast path >> happening in DPDK threads, and this is pretty much the mechanism used >> by OVDK by extending a new kind of dpif provider. But for upstream OVS >> DPDK support, I can only see netdev extension, I don't know what's the >> reason behind, can anybody post any discussion relevant on this if >> any? Do we see huge benefit when every packet going through "netdev" >> type of data path instead of a fast/slow path fashion? or I missed >> anything obvious? >> >> Thanks, >> John >> _______________________________________________ >> dev mailing list >> dev@openvswitch.org >> http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
