DPDK Summit NA 2017

1. Yasufumi Ogawa (NTT)
Tetsuro Nakamura (NTT)
DPDK Summit - San Jose – 2017
Implementation and Testing of
Soft Patch Panel

2. 2
Agenda
u Motivation
u SPP (Soft Patch Panel)
u Design and Network Configuration
u Implementation
u Performance Test
u Use-case
u PoC Implementation
u Performance Test
u Summary

3. 3
Motivation
VM ・・・VM VM VM VM VM
・・・
L2 Switch
L3 Router
Load
Balancer
MPLSFirewall
Audio
Video
Web ServiceSecurityMonitoring
DPI
Variety kinds of service apps on VMs
u Large-scale cloud for telecom services
u Service Function Chaining for virtual network appliances
u Flexibility, Maintainability and High-Performance

4. 4
Soft Patch Panel
VM VM VM VM VM
Virtual Ports
Physical Ports
u Change network path with patch panel like simple interface
u High-speed packet processing with DPDK
u Update network configuration dynamically without terminating services

5. 5
Design
Host
Guest
NFV App
vhost
MPLSFirewall
L2
Switch
Guest
NFV App
vhost
SPP
Resource Manager
(Primary)
spp_nfv
(Secondary)
spp_nfv
(Secondary)
u Multi-process Application
u Primary process is a resource
manager
u Secondary processes are workers for
packet forwarding
u Several Virtual Port Support
u ring pmd
u vhost pmd
u pcap pmd
etc

6. 6
Host
Network Configuration
Guest
NFV App
vhost
Guest
NFV App
vhost
sec#1 sec#2 sec#3
SPP
Controller
spp> sec 1; patch 0 1
spp> sec 1; patch 1 2
spp> sec 1;forward
SPP Controller Terminal
port#0
port#1
port#2
u SPP Controller manages connection between secondary processes
u Each of secondary has its connectionas patch information
u Patch can be updated dynamically while running NFV applications

7. 7
Patch Management
struct port_map {
int id;
enum port_type port_type;
struct stats *stats;
struct stats default_stats;
};
struct port {
int in_port_id;
int out_port_id;
uint16_t (*rx_func)(uint8_t,uint16_t,struct rte_mbuf **,uint16_t);
uint16_t (*tx_func)(uint8_t,uint16_t,struct rte_mbuf **,uint16_t);
};
port#0
(phy)
port#1
(phy)
port#2
(ring)
port_map[0].id = 0
port_map[0].port_type = PHY
...
ports_fwd_array[2].in_port = 2
ports_fwd_array[2].out_port=1
ports_fwd_array[2].rx_func=rx_burst()
ports_fwd_array[2].tx_func=tx_burst()
ports_fwd_array[0].in_port = -1
ports_fwd_array[0].out_port=2
ports_fwd_array[0].rx_func=rx_burst()
ports_fwd_array[0].tx_func=tx_burst()
port_map[0].id = 2
port_map[0].type = RING
...
Host
u Each of secondary has patch information and port attributes
u Patch information is managed as an array of port struct, "ports_fwd_array"
u Port ID and type is defined as an array of port_map struct, "port_map"

8. 8
Port Allocation
･･････
ring_pmd vhost_pmd

9. 9
Performance Test
SPP / OVS / SR-IOV
Host#1 Host#2
10GB
pktgen
l2fwd l2fwd l2fwd
u Compare throughput of SPP with OVS-DPDK and SR-IOV
u CPU: Xeon E5-2690v3 (12cores/24threads)
u NIC: Intel X520 DP 10GB DA/SFP+ Server Adapter
u DPDK v16.07
u Traffic: 64byte / 10GB
u Through 1-8 VMs
...
~ 8VMs

10. 10
Performance Test
(vhost)
(ivshmem)

11. 11
Usecase
u SR-IOV emulation with SPP aiming to improve maintainability
u Remove dependency for specific hardware
u Avoid fixed combination of versions of kernel and driver
Guest
Before (SR-IOV) After (SPP)
Host OS
Guest
SR-IOV NIC-A
V
F
V
F
V
F
V
F
App
NIC-A
VF driver
NIC-B
VF driver
Guest
App
NIC-A
VF driver
NIC-B
VF driver
Host OS
SPP＋ＶＦ
NIC-A NIC-B
App
Guest
App
DPDK DPDKDPDK DPDK
SR-IOV NIC-B
V
F
V
F
V
F
V
F DPDK

12. 12
SPP VF
u SPP VF is a pseudo SR-IOV functionality
u L2 switching
u MAC address filtering
u Multicast address
u Three types of workers
u Forwarder
u Classifier
u Merger
u OpenStack Plugin Support
u Neutron ML2 plugin

13. 13
u Benchmarking for classification of MAC addressing
u CPU: Xeon E5-2690v3 (12cores/24threads)
u NIC: Intel X520 DP 10GB DA/SFP+ Server Adapter
u DPDK v17.08
u Traffic: 64 - 1454byte / 10GB Host#1
Performance Test of SPP VF
classifier
forwarder
merger
Host#2
pktgen
10GB
~5GB
~5GB
forwarderVM
forwarder forwarderVM

14. 14
Performance Test of SPP VF
0.00
5.00
10.00
15.00
64byte 128byte 512byte 1454byte
0
2
4
6
8
10
64byte 128byte 512byte 1454byte
Mpps Gbps

15. 15
Summary
u SPP is a framework for Service Function Chaining for telecom services
u SPP consists of Resource Manager and Workers for updating network
configuration dynamically
u SPP VF and OpenStack ML2 plugin to reduce complexity of maintenance
http://dpdk.org/browse/apps/spp/
SPP
https://github.com/ntt-ns/Soft-Patch-Panel
SPP VF + OpenStack plugin (planed to be merged to SPP repo)

16. Questions?
Yasufumi Ogawa (NTT)
<ogawa.yasufumi@lab.ntt.co.jp>
Tetsuro Nakamura (NTT)
<tetsuro.nakamura@lab.ntt.co.jp>