Transcription
xUsing New DPDK PortRepresentor by SwitchApplication like OVSRONY EFRAIM, MELLANOX
What we brought ? Why we need? What it include ? First open source example. Mellanox solution.2
“ What we brought ?”Switch representation
Switch representation Few years ago we made a change and brought the swithdev to thekernel. All the customers wanted in DPDK DPDK 18,11 bring the switch management DPDK New API for switch representation introduced in DPDK, for switchapplication like OVS. https://doc.dpdk.org/guides/prog guide/switch representation.html4
“Why we need?”Accelerate Switch And Packet Processing
The need for ASAP2 Software Virtual Switches create performance burden: High CPU utilizationLimited ThroughputHigher LatencyVNF offload VNF packet processing is CPU boundedCommon pipeline processing elements can be done inHardware e.g flow classification, ACL drop rules etc.6
Smart NIC Smart NIC can offload the entire Datapath Embedded Switch (eSwitch) Virtual Switch implemented inside the Adapter Flow based switching Overlay tunnel (VxLAN or others) Encap/Decap SR-IOV enable direct access from VM to theAdapter Control plane and software path run in DPDK ASAP2 enables SDN on SR-IOV Separation of control and data plane Open vSwitch interfaces to the user remain untouched The hardware offloads are transparent to the userControl planeSR-IOVVMVMHypervisorSR-IOV NICeSwitchData planeUser does not need changes in his environment7
Software based vs Hardware basedTraditional Model: All SoftwareHigh Latency, Low Bandwidth, CPU IntensiveConnectX: Hardware OffloadLow Latency, High Bandwidth, Efficient CPUOVS-vswitchdOVS-vswitchdOVS DPDK DPOVS DPDK DPConnectX eSwitchFirst flow packetFallback FRWD pathHardwareHW forwarded Packets8
“What it include ?”Port representorRTE flow API
Port Representors Send packet from the host CPUto VF (OVS Re-injection)Receive of eSwitch “miss”packetsFlow configuration (add/remove)Flow statistics read for thepurposes of aging and statisticsFlowsvPort 3representor hypervisorvPort 2representorThe VF representor supportsthe following operationseSW portvPort 1representor Representor ports are aethdev modeling of eSwitchportsNet W eSwitchExt port10
“First open source example.”Open vSwitch
OVS support for HW offload Changes are made only in theDPDK datapath proto-dpifnetdev providerHW offload of flow usingrte flow.Packets forwarded by theDPDK datapath aretransmitted on therepresentors and forwarded bythe e-switch to the respectiveVF or to the wireovs-vswitchdnetdevHWoffloaddpifdpif DPDKAdd/del/stats flow action(fwd, drop,tunnel .)RTE FlowethDev1VF1datapathEhtDev2VF2EthDev npacketsconfigurationPFHW vendor drivervPortsNICeSwitch (datapath)Generic modified SW12
“Mellanox solution.”
RoCE and DPDK from the VM Overlay support HW switch Acceleration VM/ containers Packets Processing (VNF) HW overlay support (VXLAN etc)0% for switch packets 10’s Mpps to VMVMUse native Mellanox PMD over VFUse RoCE ( RDMA)VMLow latency and high Bandwidth to the VMeSwitchEncap/Decapoverlay networkheaderVXLAN14
TestASAP2 Direct OVS DPDKBenefit1 FlowVXLAN66M PPS7.6M PPS(VLAN)8.6X60K flowsVXLAN19.8M PPS1.9M PPS10.4XConnectX-5 provide significant performanceboost Without adding CPU resourcesMillion Packet Per SecondOVS over DPDK VS. OVS Offload – ConnectX-5706050404 Cores66 MPPs0 Cores302010Dedicated 7.6 MPPsMessage Rate0OVS over DPDKMessage RateOVS OffloadDedicated Hypervisor Cores15
Q&A
7 Smart NIC can offload the entire Datapath Embedded Switch (eSwitch) Virtual Switch implemented inside the Adapter Flow based switching Overlay tunnel (VxLAN or others) Encap/Decap SR-IOV enable direct access from VM to the Adapter Control plane and software path run in DPDK ASAP2 ena
