-#. **DPDK Performance Tests** - VPP is using DPDK code to control and drive
- the NICs and physical interfaces. Testpmd tests are used as a baseline to
- profile the DPDK sub-system of VPP. DPDK performance tests executed in
+#. **LXC and Docker Containers VPP memif - Performance** - VPP memif
+ virtual interface tests interconnect multiple VPP instances running in
+ containers. VPP vswitch instance runs in bare-metal user-mode
+ handling Intel x520 NIC 10GbE, Intel x710 NIC 10GbE, Intel xl710 NIC 40GbE
+ interfaces and connecting over memif (Slave side) virtual interfaces to more
+ instances of VPP running in LXC or in Docker Containers, both with memif
+ virtual interfaces (Master side). Tested across a range of multi-thread and
+ multi-core configurations. TRex is used as a traffic generator.
+
+#. **Container Topologies Orchestrated by K8s - Performance** - CSIT Container
+ topologies connected over the memif virtual interface (shared memory
+ interface). For these tests VPP vswitch instance runs in a Docker Container
+ handling Intel x520 NIC 10GbE, Intel x710 NIC 10GbE interfaces and connecting
+ over memif virtual interfaces to more instances of VPP running in Docker
+ Containers with memif virtual interfaces. All containers are
+ orchestrated by Kubernetes, with `Ligato <https://github.com/ligato>`_ for
+ container networking. TRex is used as a traffic generator.
+
+#. **DPDK Performance** - VPP is using DPDK code to control and drive
+ the NICs and physical interfaces. Tests are used as a baseline to
+ profile performance of the DPDK sub-system. DPDK tests are executed in