Ericsson and Netronome SDxCentral DemoFriday webinar featuring Nick Tausanovtich, VP of Solutions Architecture and Silicon Product Management at Netronome, and Patrick Jestin, SDN Strategic Product Manager at Ericsson, from June 3, 2016.
CSS is based on Open vSwitch with DPDK user path.
CSS has moderate to good performance, but has full SDN flexibility and networking capacity. The infrastructure handles the redundancy, thus, the VNF/application is independent of the infrastructure. However, the vSwitch is the bottleneck because the packet forwarding is done in the vSwitch.
SR-IOV has very high performance, but lacks support for SDN services beyond basic L2 and complicates Cloud management significantly. The VNF/application has to know the infrastructure and has to handle the redundancy.
Smart NIC has very high performance and full SDN flexibility and networking capacity. The OvS is handling full SDN but is not in the datapath because the switching is offloaded to the Smart NIC. The packet forwarding is handled it the Smart NIC and not in the vSwitch. The Smart NIC handles the infrastructure, thus, VNF/application is independent of the infrastructure.
Accelerates and Offloads Server Based Networking Data Path Functions
Supports virtual switching, overlay network tunneling, stateful security policies
Production firmware datapaths (e.g. OVS) provided, with options for user programming
The technical solution of the Netronome’s Smart NIC is based on a standard OvS with a modified linux kernel module. The main message is that it is seamlessly integrated with the control plane.
The ovs-vswitchd handles the complete openflow pipeline (slow path).
Whenever a packet has traversed the slow path, the vswitchd creates a flow cache entry in the kernel datapath for processing of subsequent packets of the same flow (via dpif).
Now, the modified kernel module off-loads the dpif flow cache entries into the Smart NIC for fast path acceleration (1:1). That means that no CPU load is needed for fast path acceleration.
Now, when a packet (for example for a physical – VM connection) is received, it is checked whether it’s in the flow cache. If yes, the OVS action handling is done on Smart NIC. If not, the packet handling is “swapped” to the kernel module – or even the slow path – for further processing. The red line shows the fastpath acceleration of packet which matches the flow cache in the offloaded OVS Datapath.
Note that SmartNICs and OVS can flexibly be mixed in a DC with Cloud SDN.
The current packet size is 64 bytes and the current number of packet flows is 10k. This can be modified.
We are slowly ramping up the traffic load for demonstration purpose.
The reference numbers for OVS 2.5 using 64 byte packets & 10k flows is:
1 core: 1.20 Mpps
2 cores: 2.63 Mpps
4 cores: 5.34 Mpps
8 cores: 9.13 Mpps
Netronome: 22.30 Mpps
Our SDN Controller has flexibility to control different data planes (vSwitch, SR-IOV, Smart NIC) to adapt to the different needs of VNFs
A Smart NIC datapath combines SR-IOV performance with the power, flexibility and simplicity of Cloud and Services SDN
Because our SDN solution is based on open-source (de-facto) industry standards ODL and OVS we were able to seamlessly integrate the Netronome Smart NIC within a few weeks. We expect the adoption of other Smart NICs to be similarly simple
SDN deployments with Smart NIC can even save TCO compared to vSwitch deployments for certain NFV use cases