rls1807 report: added section logical topologies in ../vpp_performance_tests/overview.rst.

Change-Id: Ied5a5caf95baddf8210b773002a8a3e5dc971a2d
Signed-off-by: Maciek Konstantynowicz <mkonstan@cisco.com>

1 files changed, 338 insertions, 221 deletions

diff --git a/docs/report/vpp_performance_tests/overview.rst b/docs/report/vpp_performance_tests/overview.rst
index d9e271e2d9..10e128bcaf 100644
--- a/docs/report/vpp_performance_tests/overview.rst
+++ b/docs/report/vpp_performance_tests/overview.rst
@@ -1,238 +1,355 @@
 Overview
 ========
 
-.. _tested_physical_topologies:
+For description of physical testbeds used for VPP performance tests
+please refer to :ref:`physical_testbeds`.
 
-Tested Physical Topologies
---------------------------
+Logical Topologies
+------------------
+
+CSIT VPP performance tests are executed on physical testbeds described
+in :ref:`physical_testbeds`. Based on the packet path thru server SUTs,
+three distinct logical topology types are used for VPP DUT data plane
+testing:
+
+#. NIC-to-NIC switching topologies.
+#. VM service switching topologies.
+#. Container service switching topologies.
+
+NIC-to-NIC Switching
+~~~~~~~~~~~~~~~~~~~~
+
+The simplest logical topology for software data plane application like
+VPP is NIC-to-NIC switching. Tested topologies for 2-Node and 3-Node
+testbeds are shown in figures below.
+
+.. only:: latex
+
+    .. raw:: latex
+
+        \begin{figure}[H]
+        \centering
+            \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-2n-nic2nic}
+            \label{fig:logical-2n-nic2nic}
+        \end{figure}
+
+.. only:: html
+
+    .. figure:: logical-2n-nic2nic.svg
+        :alt: logical-2n-nic2nic
+        :align: center
+
+
+.. only:: latex
+
+    .. raw:: latex
+
+        \begin{figure}[H]
+        \centering
+            \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-3n-nic2nic}
+            \label{fig:logical-3n-nic2nic}
+        \end{figure}
+
+.. only:: html
+
+    .. figure:: logical-3n-nic2nic.svg
+        :alt: logical-3n-nic2nic
+        :align: center
+
+Server Systems Under Test (SUT) run VPP application in Linux user-mode
+as a Device Under Test (DUT). Server Traffic Generator (TG) runs T-Rex
+application. Physical connectivity between SUTs and TG is provided using
+different drivers and NIC models that need to be tested for performance
+(packet/bandwidth throughput and latency).
+
+From SUT and DUT perspectives, all performance tests involve forwarding
+packets between two (or more) physical Ethernet ports (10GE, 25GE, 40GE,
+100GE). In most cases both physical ports on SUT are located on the same
+NIC. The only exceptions are link bonding and 100GE tests. In the latter
+case only one port per NIC can be driven at linerate due to PCIe Gen3
+x16 slot bandwidth limiations. 100GE NICs are not supported in PCIe Gen3
+x8 slots.
+
+Note that reported VPP DUT performance results are specific to the SUTs
+tested. SUTs with other processors than the ones used in FD.io lab are
+likely to yield different results. A good rule of thumb, that can be
+applied to estimate VPP packet thoughput for NIC-to-NIC switching
+topology, is to expect the forwarding performance to be proportional to
+processor core frequency for the same processor architecture, assuming
+processor is the only limiting factor and all other SUT parameters are
+equivalent to FD.io CSIT environment.
+
+VM Service Switching
+~~~~~~~~~~~~~~~~~~~~
+
+VM service switching topology test cases require VPP DUT to communicate
+with Virtual Machines (VMs) over vhost-user virtual interfaces.
+
+Two types of VM service topologies are tested in CSIT |release|:
+
+#. "Parallel" topology with packets flowing within SUT from NIC(s) via
+   VPP DUT to VM, back to VPP DUT, then out thru NIC(s).
+
+#. "Chained" topology (a.k.a. "Snake") with packets flowing within SUT
+   from NIC(s) via VPP DUT to VM, back to VPP DUT, then to the next VM,
+   back to VPP DUT and so on and so forth until the last VM in a chain,
+   then back to VPP DUT and out thru NIC(s).
+
+For each of the above topologies, VPP DUT is tested in a range of L2
+or IPv4/IPv6 configurations depending on the test suite. Sample VPP DUT
+"Chained" VM service topologies for 2-Node and 3-Node testbeds with each
+SUT running N of VM instances is shown in the figures below.
+
+.. only:: latex
+
+    .. raw:: latex
+
+        \begin{figure}[H]
+        \centering
+            \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-2n-vm-vhost}
+            \label{fig:logical-2n-vm-vhost}
+        \end{figure}
+
+.. only:: html
 
-CSIT VPP performance tests are executed on physical baremetal servers hosted by
-:abbr:`LF (Linux Foundation)` FD.io project. Testbed physical topology is shown
-in the figure below.::
-
-        +------------------------+           +------------------------+
-        |                        |           |                        |
-        |  +------------------+  |           |  +------------------+  |
-        |  |                  |  |           |  |                  |  |
-        |  |                  <----------------->                  |  |
-        |  |       DUT1       |  |           |  |       DUT2       |  |
-        |  +--^---------------+  |           |  +---------------^--+  |
-        |     |                  |           |                  |     |
-        |     |            SUT1  |           |  SUT2            |     |
-        +------------------------+           +------------------^-----+
-              |                                                 |
-              |                                                 |
-              |                  +-----------+                  |
-              |                  |           |                  |
-              +------------------>    TG     <------------------+
-                                 |           |
-                                 +-----------+
-
-SUT1 and SUT2 are two System Under Test servers (Cisco UCS C240, each with two
-Intel XEON CPUs), TG is a Traffic Generator (TG, another Cisco UCS C240, with
-two Intel XEON CPUs). SUTs run VPP SW application in Linux user-mode as a
-Device Under Test (DUT). TG runs TRex SW application as a packet Traffic
-Generator. Physical connectivity between SUTs and to TG is provided using
-different NIC models that need to be tested for performance. Currently
-installed and tested NIC models include:
-
-#. 2port10GE X520-DA2 Intel.
-#. 2port10GE X710 Intel.
-#. 2port10GE VIC1227 Cisco.
-#. 2port40GE VIC1385 Cisco.
-#. 2port40GE XL710 Intel.
-
-From SUT and DUT perspective, all performance tests involve forwarding packets
-between two physical Ethernet ports (10GE or 40GE). Due to the number of
-listed NIC models tested and available PCI slot capacity in SUT servers, in
-all of the above cases both physical ports are located on the same NIC. In
-some test cases this results in measured packet throughput being limited not
-by VPP DUT but by either the physical interface or the NIC capacity.
-
-Going forward CSIT project will be looking to add more hardware into FD.io
-performance labs to address larger scale multi-interface and multi-NIC
-performance testing scenarios.
-
-For service chain topology test cases that require DUT (VPP) to communicate with
-VirtualMachines (VMs) or with Linux/Docker Containers (Ctrs) over
-vhost-user/memif interfaces, N of VM/Ctr instances are created on SUT1
-and SUT2. Three types of service chain topologies are tested in CSIT |release|:
-
-#. "Parallel" topology with packets flowing from NIC via DUT (VPP) to
-   VM/Container and back to VPP and NIC;
-
-#. "Chained" topology (a.k.a. "Snake") with packets flowing via DUT (VPP) to
-   VM/Container, back to DUT, then to the next VM/Container, back to DUT and
-   so on until the last VM/Container in a chain, then back to DUT and NIC;
-
-#. "Horizontal" topology with packets flowing via DUT (VPP) to Container,
-   then via "horizontal" memif to the next Container, and so on until the
-   last Container, then back to DUT and NIC. "Horizontal" topology is not
-   supported for VMs;
-
-For each of the above topologies, DUT (VPP) is tested in a range of L2
-or IPv4/IPv6 configurations depending on the test suite. A sample DUT
-"Chained" service topology with N of VM/Ctr instances is shown in the
-figure below. Packet flow thru the DUTs and VMs/Ctrs is marked with
-``***``::
-
-        +-------------------------+           +-------------------------+
-        | +---------+ +---------+ |           | +---------+ +---------+ |
-        | |VM/Ctr[1]| |VM/Ctr[N]| |           | |VM/Ctr[1]| |VM/Ctr[N]| |
-        | |  *****  | |  *****  | |           | |  *****  | |  *****  | |
-        | +--^---^--+ +--^---^--+ |           | +--^---^--+ +--^---^--+ |
-        |   *|   |*     *|   |*   |           |   *|   |*     *|   |*   |
-        | +--v---v-------v---v--+ |           | +--v---v-------v---v--+ |
-        | |  *   *       *   *  |*|***********|*|  *   *       *   *  | |
-        | |  *   *********   ***<-|-----------|->***   *********   *  | |
-        | |  *    DUT1          | |           | |       DUT2       *  | |
-        | +--^------------------+ |           | +------------------^--+ |
-        |   *|                    |           |                    |*   |
-        |   *|            SUT1    |           |  SUT2              |*   |
-        +-------------------------+           +-------------------------+
-            *|                                                     |*
-            *|                                                     |*
-            *|                    +-----------+                    |*
-            *|                    |           |                    |*
-            *+-------------------->    TG     <--------------------+*
-            **********************|           |**********************
-                                  +-----------+
-
-In above "Chained" topology, packets are switched by DUT multiple times:
-twice for a single VM/Ctr, three times for two VMs/Ctrs, N+1 times for N
-VMs/Ctrs. Hence the external throughput rates measured by TG and listed
-in this report must be multiplied by (N+1) to represent the actual DUT
+    .. figure:: logical-2n-vm-vhost.svg
+        :alt: logical-2n-vm-vhost
+        :align: center
+
+
+.. only:: latex
+
+    .. raw:: latex
+
+        \begin{figure}[H]
+        \centering
+            \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-3n-vm-vhost}
+            \label{fig:logical-3n-vm-vhost}
+        \end{figure}
+
+.. only:: html
+
+    .. figure:: logical-3n-vm-vhost.svg
+        :alt: logical-3n-vm-vhost
+        :align: center
+
+In "Chained" VM topologies, packets are switched by VPP DUT multiple
+times: twice for a single VM, three times for two VMs, N+1 times for N
+VMs. Hence the external throughput rates measured by TG and listed in
+this report must be multiplied by N+1 to represent the actual VPP DUT
 aggregate packet forwarding rate.
 
+For "Parallel" service topology packets are always switched twice by VPP
+DUT per service chain.
+
+Note that reported VPP DUT performance results are specific to the SUTs
+tested. SUTs with other processor than the ones used in FD.io lab are
+likely to yield different results. Similarly to NIC-to-NIC switching
+topology, here one can also expect the forwarding performance to be
+proportional to processor core frequency for the same processor
+architecture, assuming processor is the only limiting factor. However
+due to much higher dependency on intensive memory operations in VM
+service chained topologies and sensitivity to Linux scheduler settings
+and behaviour, this estimation may not always yield good enough
+accuracy.
+
+Container Service Switching
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Container service switching topology test cases require VPP DUT to
+communicate with Containers (Ctrs) over memif virtual interfaces.
+
+Three types of VM service topologies are tested in CSIT |release|:
+
+#. "Parallel" topology with packets flowing within SUT from NIC(s) via
+   VPP DUT to Container, back to VPP DUT, then out thru NIC(s).
+
+#. "Chained" topology (a.k.a. "Snake") with packets flowing within SUT
+   from NIC(s) via VPP DUT to Container, back to VPP DUT, then to the
+   next Container, back to VPP DUT and so on and so forth until the
+   last Container in a chain, then back to VPP DUT and out thru NIC(s).
+
+#. "Horizontal" topology with packets flowing within SUT from NIC(s) via
+   VPP DUT to Container, then via "horizontal" memif to the next
+   Container, and so on and so forth until the last Container, then
+   back to VPP DUT and out thru NIC(s).
+
+For each of the above topologies, VPP DUT is tested in a range of L2
+or IPv4/IPv6 configurations depending on the test suite. Sample VPP DUT
+"Chained" Container service topologies for 2-Node and 3-Node testbeds
+with each SUT running N of Container instances is shown in the figures
+below.
+
+.. only:: latex
+
+    .. raw:: latex
+
+        \begin{figure}[H]
+        \centering
+            \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-2n-container-memif}
+            \label{fig:logical-2n-container-memif}
+        \end{figure}
+
+.. only:: html
+
+    .. figure:: logical-2n-container-memif.svg
+        :alt: logical-2n-container-memif
+        :align: center
+
+
+.. only:: latex
+
+    .. raw:: latex
+
+        \begin{figure}[H]
+        \centering
+            \includesvg[width=0.90\textwidth]{../_tmp/src/vpp_performance_tests/logical-3n-container-memif}
+            \label{fig:logical-3n-container-memif}
+        \end{figure}
+
+.. only:: html
+
+    .. figure:: logical-3n-container-memif.svg
+        :alt: logical-3n-container-memif
+        :align: center
+
+In "Chained" Container topologies, packets are switched by VPP DUT
+multiple times: twice for a single Container, three times for two
+Containers, N+1 times for N Containers. Hence the external throughput
+rates measured by TG and listed in this report must be multiplied by N+1
+to represent the actual VPP DUT aggregate packet forwarding rate.
+
 For a "Parallel" and "Horizontal" service topologies packets are always
-switched by DUT twice per service chain.
-
-Note that reported DUT (VPP) performance results are specific to the SUTs
-tested. Current :abbr:`LF (Linux Foundation)` FD.io SUTs are based on Intel
-XEON E5-2699v3 2.3GHz CPUs. SUTs with other CPUs are likely to yield different
-results. A good rule of thumb, that can be applied to estimate VPP packet
-thoughput for Phy-to-Phy (NIC-to-NIC, PCI-to-PCI) topology, is to expect
-the forwarding performance to be proportional to CPU core frequency,
-assuming CPU is the only limiting factor and all other SUT parameters
-equivalent to FD.io CSIT environment. The same rule of thumb can be also
-applied for Phy-to-VM/Ctr-to-Phy (NIC-to-VM/Ctr-to-NIC) topology, but due to
-much higher dependency on intensive memory operations and sensitivity to Linux
-kernel scheduler settings and behaviour, this estimation may not always yield
-good enough accuracy.
-
-For detailed FD.io CSIT testbed specification and topology, as well as
-configuration and setup of SUTs and DUTs testbeds please refer to
-:ref:`test_environment`.
-
-Similar SUT compute node can be arrived to in a standalone VPP setup by using a
-`vpp-config configuration tool
-<https://wiki.fd.io/view/VPP/Configuration_Tool>`_ developed within the
-VPP project using CSIT recommended settings and scripts.
+switched by VPP DUT twice per service chain.
+
+Note that reported VPP DUT performance results are specific to the SUTs
+tested. SUTs with other processor than the ones used in FD.io lab are
+likely to yield different results. Similarly to NIC-to-NIC switching
+topology, here one can also expect the forwarding performance to be
+proportional to processor core frequency for the same processor
+architecture, assuming processor is the only limiting factor. However
+due to much higher dependency on intensive memory operations in
+Container service chained topologies and sensitivity to Linux scheduler
+settings and behaviour, this estimation may not always yield good enough
+accuracy.
 
 Performance Tests Coverage
 --------------------------
 
-Performance tests are split into two main categories:
-
-- Throughput discovery - discovery of packet forwarding rate using binary search
-  in accordance to :rfc:`2544`.
-
-  - NDR - discovery of Non Drop Rate packet throughput, at zero packet loss;
-    followed by one-way packet latency measurements at 10%, 50% and 100% of
-    discovered NDR throughput.
-  - PDR - discovery of Partial Drop Rate, with specified non-zero packet loss
-    currently set to 0.5%; followed by one-way packet latency measurements at
-    100% of discovered PDR throughput.
-
-CSIT |release| includes following performance test suites, listed per NIC type:
-
-- 2port10GE X520-DA2 Intel
-
-  - **L2XC** - L2 Cross-Connect switched-forwarding of untagged, dot1q, dot1ad
-    VLAN tagged Ethernet frames.
-  - **L2BD** - L2 Bridge-Domain switched-forwarding of untagged Ethernet frames
-    with MAC learning; disabled MAC learning i.e. static MAC tests to be added.
-  - **L2BD Scale** - L2 Bridge-Domain switched-forwarding of untagged Ethernet
-    frames with MAC learning; disabled MAC learning i.e. static MAC tests to be
-    added with 20k, 200k and 2M FIB entries.
-  - **IPv4** - IPv4 routed-forwarding.
-  - **IPv6** - IPv6 routed-forwarding.
-  - **IPv4 Scale** - IPv4 routed-forwarding with 20k, 200k and 2M FIB entries.
-  - **IPv6 Scale** - IPv6 routed-forwarding with 20k, 200k and 2M FIB entries.
-  - **VMs with vhost-user** - virtual topologies with 1 VM and service chains
-    of 2 VMs using vhost-user interfaces, with VPP forwarding modes incl. L2
-    Cross-Connect, L2 Bridge-Domain, VXLAN with L2BD, IPv4 routed-forwarding.
-  - **COP** - IPv4 and IPv6 routed-forwarding with COP address security.
-  - **ACL** - L2 Bridge-Domain switched-forwarding and IPv4 and IPv6 routed-
-    forwarding with iACL and oACL IP address, MAC address and L4 port security.
-  - **LISP** - LISP overlay tunneling for IPv4-over-IPv4, IPv6-over-IPv4,
-    IPv6-over-IPv6, IPv4-over-IPv6 in IPv4 and IPv6 routed-forwarding modes.
-  - **VXLAN** - VXLAN overlay tunnelling integration with L2XC and L2BD.
-  - **QoS Policer** - ingress packet rate measuring, marking and limiting
-    (IPv4).
-  - **NAT** - (Source) Network Address Translation tests with varying
-    number of users and ports per user.
-  - **Container memif connections** - VPP memif virtual interface tests to
-    interconnect VPP instances with L2XC and L2BD.
-  - **Container K8s Orchestrated Topologies** - Container topologies connected
-    over the memif virtual interface.
-  - **SRv6** - Segment Routing IPv6 tests.
-
-- 2port40GE XL710 Intel
-
-  - **L2XC** - L2 Cross-Connect switched-forwarding of untagged Ethernet frames.
-  - **L2BD** - L2 Bridge-Domain switched-forwarding of untagged Ethernet frames
-    with MAC learning.
-  - **IPv4** - IPv4 routed-forwarding.
-  - **IPv6** - IPv6 routed-forwarding.
-  - **VMs with vhost-user** - virtual topologies with 1 VM and service chains
-    of 2 VMs using vhost-user interfaces, with VPP forwarding modes incl. L2
-    Cross-Connect, L2 Bridge-Domain, VXLAN with L2BD, IPv4 routed-forwarding.
-  - **IPSecSW** - IPSec encryption with AES-GCM, CBC-SHA1 ciphers, in
-    combination with IPv4 routed-forwarding.
-  - **IPSecHW** - IPSec encryption with AES-GCM, CBC-SHA1 ciphers, in
-    combination with IPv4 routed-forwarding. Intel QAT HW acceleration.
-  - **IPSec+LISP** - IPSec encryption with CBC-SHA1 ciphers, in combination
-    with LISP-GPE overlay tunneling for IPv4-over-IPv4.
-  - **VPP TCP/IP stack** - tests of VPP TCP/IP stack used with VPP built-in HTTP
-    server.
-  - **Container memif connections** - VPP memif virtual interface tests to
-    interconnect VPP instances with L2XC and L2BD.
-
-- 2port10GE X710 Intel
-
-  - **L2BD** - L2 Bridge-Domain switched-forwarding of untagged Ethernet frames
-    with MAC learning.
-  - **VMs with vhost-user** - virtual topologies with 1 VM using vhost-user
-    interfaces, with VPP forwarding modes incl. L2 Bridge-Domain.
-  - **Container memif connections** - VPP memif virtual interface tests to
-    interconnect VPP instances with L2XC and L2BD.
-  - **Container K8s Orchestrated Topologies** - Container topologies connected
-    over the memif virtual interface.
-
-- 2port10GE VIC1227 Cisco
-
-  - **L2BD** - L2 Bridge-Domain switched-forwarding of untagged Ethernet frames
-    with MAC learning.
-
-- 2port40GE VIC1385 Cisco
-
-  - **L2BD** - L2 Bridge-Domain switched-forwarding of untagged Ethernet frames
-     with MAC learning.
-
-Execution of performance tests takes time, especially the throughput discovery
-tests. Due to limited HW testbed resources available within FD.io labs hosted
-by :abbr:`LF (Linux Foundation)`, the number of tests for NICs other than X520
-(a.k.a. Niantic) has been limited to few baseline tests. CSIT team expect the
-HW testbed resources to grow over time, so that complete set of performance
-tests can be regularly and(or) continuously executed against all models of
-hardware present in FD.io labs.
+Performance tests measure following metrics for tested VPP DUT
+topologies and configurations:
+
+- Packet Throughput: measured in accordance with :rfc:`2544`, using
+  FD.io CSIT Multiple Loss Ratio search (MLRsearch), an optimized binary
+  search algorithm, producing throughput at different Packet Loss Ratio
+  (PLR) values:
+
+  - Non Drop Rate (NDR): packet throughput at PLR=0%.
+  - Partial Drop Rate (PDR): packet throughput at PLR=0.5%.
+
+- One-Way Packet Latency: measured at different offered packet loads:
+
+  - 100% of discovered NDR throughput.
+  - 100% of discovered PDR throughput.
+
+- Maximum Receive Rate (MRR): measure packet forwarding rate under the
+  maximum load offered by traffic generator over a set trial duration,
+  regardless of packet loss. Maximum load for specified Ethernet frame
+  size is set to the bi-directional link rate.
+
+CSIT |release| includes following performance test areas covered across
+a range of NIC drivers and NIC models:
+
++-----------------------+----------------------------------------------+
+| Test Area             |  Description                                 |
++=======================+==============================================+
+| ACL                   | L2 Bridge-Domain switching and               |
+|                       | IPv4and IPv6 routing with iACL and oACL IP   |
+|                       | address, MAC address and L4 port security.   |
++-----------------------+----------------------------------------------+
+| COP                   | IPv4 and IPv6 routing with COP address       |
+|                       | security.                                    |
++-----------------------+----------------------------------------------+
+| IPv4                  | IPv4 routing.                                |
++-----------------------+----------------------------------------------+
+| IPv6                  | IPv6 routing.                                |
++-----------------------+----------------------------------------------+
+| IPv4 Scale            | IPv4 routing with 20k, 200k and 2M FIB       |
+|                       | entries.                                     |
++-----------------------+----------------------------------------------+
+| IPv6 Scale            | IPv6 routing with 20k, 200k and 2M FIB       |
+|                       | entries.                                     |
++-----------------------+----------------------------------------------+
+| IPSecHW               | IPSec encryption with AES-GCM, CBC-SHA1      |
+|                       | ciphers, in combination with IPv4 routing.   |
+|                       | Intel QAT HW acceleration.                   |
++-----------------------+----------------------------------------------+
+| IPSec+LISP            | IPSec encryption with CBC-SHA1 ciphers, in   |
+|                       | combination with LISP-GPE overlay tunneling  |
+|                       | for IPv4-over-IPv4.                          |
++-----------------------+----------------------------------------------+
+| IPSecSW               | IPSec encryption with AES-GCM, CBC-SHA1      |
+|                       | ciphers, in combination with IPv4 routing.   |
++-----------------------+----------------------------------------------+
+| K8s Containers Memif  | K8s orchestrated container VPP service chain |
+|                       | topologies connected over the memif virtual  |
+|                       | interface.                                   |
++-----------------------+----------------------------------------------+
+| KVM VMs vhost-user    | Virtual topologies with service              |
+|                       | chains of 1 and 2 VMs using vhost-user       |
+|                       | interfaces, with different VPP forwarding    |
+|                       | modes incl. L2XC, L2BD, VXLAN with L2BD,     |
+|                       | IPv4 routing.                                |
++-----------------------+----------------------------------------------+
+| L2BD                  | L2 Bridge-Domain switching of untagged       |
+|                       | Ethernet frames with MAC learning; disabled  |
+|                       | MAC learning i.e. static MAC tests to be     |
+|                       | added.                                       |
++-----------------------+----------------------------------------------+
+| L2BD Scale            | L2 Bridge-Domain switching of untagged       |
+|                       | Ethernet frames with MAC learning; disabled  |
+|                       | MAC learning i.e. static MAC tests to be     |
+|                       | added with 20k, 200k and 2M FIB entries.     |
++-----------------------+----------------------------------------------+
+| L2XC                  | L2 Cross-Connect switching of untagged,      |
+|                       | dot1q, dot1ad VLAN tagged Ethernet frames.   |
++-----------------------+----------------------------------------------+
+| LISP                  | LISP overlay tunneling for IPv4-over-IPv4,   |
+|                       | IPv6-over-IPv4, IPv6-over-IPv6,              |
+|                       | IPv4-over-IPv6 in IPv4 and IPv6 routing      |
+|                       | modes.                                       |
++-----------------------+----------------------------------------------+
+| LXC/DRC Containers    | Container VPP memif virtual interface tests  |
+| Memif                 | with different VPP forwarding modes incl.    |
+|                       | L2XC, L2BD.                                  |
++-----------------------+----------------------------------------------+
+| NAT                   | (Source) Network Address Translation tests   |
+|                       | with varying number of users and ports per   |
+|                       | user.                                        |
++-----------------------+----------------------------------------------+
+| QoS Policer           | Ingress packet rate measuring, marking and   |
+|                       | limiting (IPv4).                             |
++-----------------------+----------------------------------------------+
+| SRv6 Routing          | Segment Routing IPv6 tests.                  |
++-----------------------+----------------------------------------------+
+| VPP TCP/IP stack      | Tests of VPP TCP/IP stack used with VPP      |
+|                       | built-in HTTP server.                        |
++-----------------------+----------------------------------------------+
+| VXLAN                 | VXLAN overlay tunnelling integration with    |
+|                       | L2XC and L2BD.                               |
++-----------------------+----------------------------------------------+
+
+Execution of performance tests takes time, especially the throughput
+tests. Due to limited HW testbed resources available within FD.io labs
+hosted by :abbr:`LF (Linux Foundation)`, the number of tests for some
+NIC models has been limited to few baseline tests.
 
 Performance Tests Naming
 ------------------------
 
-CSIT |release| follows a common structured naming convention for all performance
-and system functional tests, introduced in CSIT rls1701.
+FD.io CSIT |release| follows a common structured naming convention for
+all performance and system functional tests, introduced in CSIT rls1701.
 
-The naming should be intuitive for majority of the tests. Complete description
-of CSIT test naming convention is provided on :ref:`csit_test_naming`.
+The naming should be intuitive for majority of the tests. Complete
+description of FD.io CSIT test naming convention is provided on
+:ref:`csit_test_naming`.