Detailed instructions for simplified steps 1-3 below, can be found on VPP Quick Start Guide.
SPDK supports VPP version 18.01.1.
Please skip this step if using already built packages.
Clone and checkout VPP
Install VPP build dependencies
Build and create .rpm packages
Alternatively, build and create .deb packages
Packages can be found in
For more in depth instructions please see Building section in VPP documentation
Please note: VPP 18.01.1 does not support OpenSSL 1.1. It is suggested to install a compatibility package for compilation time.
Then reinstall latest OpenSSL devel package:
Packages can be installed from a distribution repository or built in previous step. Minimal set of packages consists of
Note: Please remove or modify /etc/sysctl.d/80-vpp.conf file with appropriate values dependent on number of hugepages that will be used on system.
VPP takes over any network interfaces that were bound to userspace driver, for details please see DPDK guide on Binding and Unbinding Network Ports to/from the Kernel Modules.
VPP is installed as service and disabled by default. To start VPP with default config:
vpp binary directly
A usefull tool is
vppctl, that allows to control running VPP instance. Either by entering VPP configuration prompt
Or, by sending single command directly. For example to display interfaces within VPP:
For functional test purposes a virtual tap interface can be created, so no additional network hardware is required. This will allow network communication between SPDK iSCSI target using VPP end of tap and kernel iSCSI initiator using the kernel part of tap. A single host is used in this scenario.
Create tap interface via VPP
Assign address on kernel interface
To verify connectivity
Support for VPP can be built into SPDK by using configuration option.
Alternatively, directory with built libraries can be pointed at and will be used for compilation instead of installed packages.
VPP application has to be started before SPDK application, in order to enable usage of network interfaces. For example, if you use SPDK iSCSI target or NVMe-oF target, after the initialization finishes, interfaces configured within VPP will be available to be configured as portal addresses.
Moreover, you do not need to specifiy which TCP sock implementation (e.g., posix, VPP) to be used through configuration file or RPC call. Since SPDK program automatically determines the protocol according to the configured portal addresses info. For example, you can specify a Listen address in NVMe-oF subsystem configuration such as "Listen TCP 10.0.0.1:4420". SPDK programs automatically uses different implemenation to listen this provided portal info via posix or vpp implemenation(if compiled in SPDK program), and only one implementation can successfully listen on the provided portal.