DPVS is a high performance Layer-4 load balancer based on DPDK. It’s derived from Linux LVS and its modification alibaba/LVS.

the name DPVS comes from “DPDK-LVS”.

Different techniques are applied for high performance:

• Kernel by-pass (user space implementation)
• Share-nothing, per-CPU for key data (Lockless)
• RX Steering and CPU affinity (avoid context switch)
• Batching TX/RX
• Zero Copy (avoid packet copy and syscalls).
• Polling instead of interrupt.
• lockless message for high performance ICP.
• other techs enhanced by DPDK

Major features of DPVS including:

• L4 Load Balancer, including FNAT, DR mode, etc.
• Different schedule algorithm like RR, WLC, WRR, etc.
• User-space Lite IP stack(IPv4, Routing, ARP, ICMP …) .
• SNAT mode for Internet access from internal network.
• Support KNI.VLAN.Bonding for different IDC environment.
• Security aspect, support TCP syn-proxy.Conn-Limit.black-list
• QoS: Traffic Control (Ongoing)

DPVS feature modules are illustrated as following picture.

This quick start is tested with the environment below.

• Linux Distribution: CentOS 7.2
• The Kernel: 3.10.0-327. El7. X86_64
• CPU: Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
• NIC: Intel X540
• Memory: 64G and NUMA system.
• GCC: gcc version 4.8.5 20150623 (Red Hat 4.8.5-4)

Other environment should also OK if DPDK works, pls check dpdk.org for more info.

Currently, DPDK-16.07 is used for DPVS and latest DPDK stable version will be integrated soon.

You can skip this section if experienced with DPDK, and refer the link for details.

$wget HTTP: / / http://fast.dpdk.org/rel/dpdk-16.07.2.tar.xz# download from dpdk.org if link failed.$tar VXF DPDK - 16.07.2. Tar. XzCopy the code

There’s a patch for DPDK kni driver for hardware multicast, apply it if needed (for example, launch ospfd on kni device).

Assuming we are in DPVS root dir and DPDK-stables -16.07.2 is under it, PLS note it’s not mandatory, just for convenience.

$CD < path-of-dpVS > $cp patch/ dPDK-16.07/0001 - Kini-use-netlink-event-for-multicast -driver-part.patch Dpdk-stably -16.07.2/ $CD dPDk-stably -16.07.2/ $patch-n 1 < 0001- Kuni-use-netlink-event-for-multicast -driver-part.patchCopy the code

Now build DPDK and export RTE_SDK env variable for DPDK app (DPVS).

$ cd$make config T=x86_64-native linuxapp-gcc Configuration dPDk-stables -16.07.2/ $make config T=x86_64-native linuxapp-gcc Configurationdone
$ make # or make -j40 to save time, where 40 is the cpu core number.
$ export RTE_SDK=$PWDCopy the code

In our tutorial, RTE_TARGET is not set, the value is “build” by default, Thus DPDK libs and header files can be found in DPDK-stable-16.07.2 /build. It could be other values.

Now to set up DPDK hugepage, our test environment is NUMA system. For single-node system pls refer the link.

$ # for NUMA machine
$ echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
$ echo 1024 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages

$ mkdir /mnt/huge
$ mount -t hugetlbfs nodev /mnt/hugeCopy the code

Install Kernel modules and bind NIC with igb_uio driver. Quick start uses only one NIC, normally we use 2 for Full-NAT cluster, even 4 for bonding mode. Assuming eth0 will be used for DPVS/DPDK, and another standalone Linux NIC for debug, for example, eth1.

$ modprob uio
$ cdDpdk-stably -16.07.2/ $insmod build/kmod/igb_uio.ko $insmod build/kmod/rte_kni.ko $./tools/dpdk-devbind.py --st $ ifconfig eth0 down#Assuming eth0 is 0000: surf. 0$./tools/dpdk-devbind.py -b igb_uio 0000:06:00.0Copy the code

dpdk-devbind.py -u can be used to unbind driver and switch it back to Linux driver like ixgbe. You can also use lspci or ethtool -i eth0 to check the NIC PCI bus-id. Pls see DPDK site for details.

Now, dpvs.conf must be put at /etc/dpvs.conf, just copy it from conf/dpvs.conf.single-nic.sample.

$ cp conf/dpvs.conf.single-nic.sample /etc/dpvs.confCopy the code

and start DPVS,

$ cd <path-of-dpvs>/bin
$ ./dpvs &Copy the code

Check if it’s get started ?

$ ./dpip link show
1: dpdk0: socket 0 mtu 1500 rx-queue 8 tx-queue 8
    UP 10000 Mbps full-duplex fixed-nego promisc-off
    addr A0:36:9F:9D:61:F4 OF_RX_IP_CSUM OF_TX_IP_CSUM OF_TX_TCP_CSUM OF_TX_UDP_CSUMCopy the code

If you see this message. Well done, DPVS is working with NIC dpdk0!

Don’t worry if you see this error,

EAL: Error - exiting with code: 1 Cause: ports in DPDK RTE (2) ! = ports in dpvs.conf(1)Copy the code

it means the NIC used by DPVS is not match /etc/dpvs.conf. Pls use dpdk-devbind to adjust the NIC number or modify dpvs.conf. We’ll improve this part to make DPVS more “clever” to avoid modify config file when NIC count is not match.

Set VIP and Local IP (LIP, needed by Full-NAT mode) on DPVS. Let’s put commands into setup.sh. You do some check by ./ipvsadm -ln, ./dpip addr show.

Sh VIP=192.168.100.100 LIP=192.168.100.200 RS=192.168.100.2./dpip addr add${VIP}/24 dev dpdk0
./ipvsadm -A -t ${VIP}:80 -s rr
./ipvsadm -a -t ${VIP}:80 -r ${RS} -b

./ipvsadm --add-laddr -z ${LIP}-t 192.168.100.100:80 -f dpdk0 $$./setup.shCopy the code

Access VIP from Client, it looks good!

Client $curl 192.168.100.100 Your IP :port: 192.168.100.3:56890Copy the code