rls1801 report - static content edits - vpp performance.

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

diff --git a/docs/report/csit_framework_documentation/csit_design.rst b/docs/report/csit_framework_documentation/csit_design.rst
index fef0285..3e6ae66 100644 (file)
--- a/docs/report/csit_framework_documentation/csit_design.rst
+++ b/docs/report/csit_framework_documentation/csit_design.rst
@@ -108,7 +108,7 @@ A brief bottom-up description is provided here:
      - DPDK-Testpmd;
      - DPDK-L3Fwd;
      - Honeycomb;
      - DPDK-Testpmd;
      - DPDK-L3Fwd;
      - Honeycomb;

-     - VPP Container orchestrated topologies;
+     - VPP Container K8s orchestrated topologies;

 
    - Tools:
 
 
    - Tools:
 

diff --git a/docs/report/introduction/general_notes.rst b/docs/report/introduction/general_notes.rst
index 5213a6a..994a53e 100644 (file)
--- a/docs/report/introduction/general_notes.rst
+++ b/docs/report/introduction/general_notes.rst
@@ -42,7 +42,7 @@ is listed separately, as follows:
 
 #. **DPDK Performance** - VPP is using DPDK code to control and drive
    the NICs and physical interfaces. Tests are used as a baseline to
 
 #. **DPDK Performance** - VPP is using DPDK code to control and drive
    the NICs and physical interfaces. Tests are used as a baseline to

-   profile the DPDK sub-system of VPP. DPDK performance tests executed in
+   profile performance of the DPDK sub-system. DPDK tests are executed in

    physical FD.io testbeds, focusing on Testpmd/L3FWD data plane performance for
    Phy-to-Phy (NIC-to-NIC). Tests cover a range of NICs, 10GE and 40GE
    interfaces, range of multi-thread and multi-core configurations.
    physical FD.io testbeds, focusing on Testpmd/L3FWD data plane performance for
    Phy-to-Phy (NIC-to-NIC). Tests cover a range of NICs, 10GE and 40GE
    interfaces, range of multi-thread and multi-core configurations.

diff --git a/docs/report/vpp_performance_tests/csit_release_notes.rst b/docs/report/vpp_performance_tests/csit_release_notes.rst
index d029bd0..5427531 100644 (file)
--- a/docs/report/vpp_performance_tests/csit_release_notes.rst
+++ b/docs/report/vpp_performance_tests/csit_release_notes.rst
@@ -8,19 +8,26 @@ Changes in CSIT |release|
 \r
    - **Container Topologies Orchestrated by K8s with VPP memif tests**\r
 \r
 \r
    - **Container Topologies Orchestrated by K8s with VPP memif tests**\r
 \r

-     - Added tests with VPP in L2 Cross-Connect and Bridge-Domain configurations\r
-       connecting over memif virtual interfaces VPPs running in Docker\r
-       containers, with service chain topologies orchestrated by Kubernetes.\r
-       Chained, horizontal and standalone linked topologies added;\r
+   - Added tests with VPP in L2 Cross-Connect and Bridge-Domain\r
+     configurations containers, with service chain topologies orchestrated by\r
+     Kubernetes. Added following forwarding topologies: i) "Parallel" with\r
+     packets flowing from NIC via VPP to container and back to VPP and NIC;\r
+     ii) "Chained" a.k.a. "Snake" with packets flowing via VPP to container,\r
+     back to VPP, to next container, back to VPP and so on until the last\r
+     container in chain, then back to VPP and NIC; iii) "Horizontal" with\r
+     packets flowing via VPP to container, then via "horizontal" memif to\r
+     next container, and so on until the last container, then back to VPP and\r
+     NIC;.\r

 \r
    - **VPP TCP/IP stack**\r
 \r
 \r
    - **VPP TCP/IP stack**\r
 \r

-     - Added tests with VPP builtin TCP based HTTP server. WRK traffic generator\r
-       is used.\r
+     - Added tests for VPP TCP/IP stack using VPP built-in HTTP server.\r
+       WRK traffic generator is used as a client-side.\r

 \r
    - **SRv6 tests**\r
 \r
 \r
    - **SRv6 tests**\r
 \r

-     - [placeholder]\r
+     - Initial SRv6 tests verifying performance of SRv6 encapsulation and\r
+       decapsulation and SID lookups.\r

 \r
    - **IPSecSW tests**\r
 \r
 \r
    - **IPSecSW tests**\r
 \r


@@ -29,9 +36,9 @@ Changes in CSIT |release|
 \r
 #. Presentation and Analytics Layer\r
 \r
 \r
 #. Presentation and Analytics Layer\r
 \r

-     - Added multi-core scale-up analysis into Presentation and Analytics Layer\r
-       (PAL) for automated CSIT test results analysis;\r
-\r
+     - Added throughput speedup analysis for multi-core and multi-thread\r
+       VPP tests into Presentation and Analytics Layer (PAL) for automated\r
+       CSIT test results analysis;\r

 \r
 #. Other improvements\r
 \r
 \r
 #. Other improvements\r
 \r

diff --git a/docs/report/vpp_performance_tests/documentation/containers.rst b/docs/report/vpp_performance_tests/documentation/containers.rst
index a617386..b7c1b01 100644 (file)
--- a/docs/report/vpp_performance_tests/documentation/containers.rst
+++ b/docs/report/vpp_performance_tests/documentation/containers.rst
@@ -140,8 +140,8 @@ a range of virtual networking topologies.
   of functionality is better supported in LXC 2.1 but can be done is current
   version as well.
 
   of functionality is better supported in LXC 2.1 but can be done is current
   version as well.
 

-- CSIT code is currently using cgroup control the range of CPU cores the
-  container must run on. VPP thread pinning defined vpp startup.conf.
+- CSIT code is currently using cgroup to control the range of CPU cores the
+  LXC container runs on. VPP thread pinning is defined vpp startup.conf.

 
 Docker
 ~~~~~~
 
 Docker
 ~~~~~~


@@ -176,10 +176,6 @@ K8s pod definitions including compute resource allocation is provided in
 CSIT uses K8s and its infrastructure components like etcd to control all
 phases of container based virtualized network topologies.
 
 CSIT uses K8s and its infrastructure components like etcd to control all
 phases of container based virtualized network topologies.
 

-**Open Questions**
-
-- Clarify the functions provided by Contiv and Calico in Ligato system?
-

 Ligato
 ~~~~~~
 
 Ligato
 ~~~~~~
 


@@ -189,8 +185,6 @@ using goVPP [govpp]_ and vpp-agent [vpp-agent]_.
 
 **Known Issues**
 
 
 **Known Issues**
 

-**Open Questions**
-

 - Currently using a separate LF Jenkins job for building csit-centric
   prod_vpp_agent docker images vs. dockerhub/ligato ones.
 
 - Currently using a separate LF Jenkins job for building csit-centric
   prod_vpp_agent docker images vs. dockerhub/ligato ones.
 


@@ -523,11 +517,16 @@ Following container networking topologies are tested in CSIT |release|:
 
 - Kubernetes/Ligato topologies:
 
 
 - Kubernetes/Ligato topologies:
 

-  - eth-1drcl2xcbase-eth-2memif-1drcl2xc.
-  - eth-1drcl2xcbase-eth-4memif-2drcl2xc.
-  - eth-1drcl2bdbasemaclrn-eth-2memif-1drcl2xc.
-  - eth-1drcl2bdbasemaclrn-eth-4memif-2drcl2xc.
-
+  - eth-1drcl2bdbasemaclrn-eth-2memif-1drcl2xc-1paral
+  - eth-1drcl2bdbasemaclrn-eth-2memif-2drcl2xc-1horiz
+  - eth-1drcl2bdbasemaclrn-eth-2memif-4drcl2xc-1horiz
+  - eth-1drcl2bdbasemaclrn-eth-4memif-2drcl2xc-1chain
+  - eth-1drcl2bdbasemaclrn-eth-8memif-4drcl2xc-1chain
+  - eth-1drcl2xcbase-eth-2memif-1drcl2xc-1paral
+  - eth-1drcl2xcbase-eth-2memif-2drcl2xc-1horiz
+  - eth-1drcl2xcbase-eth-2memif-4drcl2xc-1horiz
+  - eth-1drcl2xcbase-eth-4memif-2drcl2xc-1chain
+  - eth-1drcl2xcbase-eth-8memif-4drcl2xc-1chain

 
 References
 ----------
 
 References
 ----------

diff --git a/docs/report/vpp_performance_tests/overview.rst b/docs/report/vpp_performance_tests/overview.rst
index 38e76d2..d835df4 100644 (file)
--- a/docs/report/vpp_performance_tests/overview.rst
+++ b/docs/report/vpp_performance_tests/overview.rst
@@ -162,7 +162,7 @@ CSIT |release| includes following performance test suites, listed per NIC type:
     number of users and ports per user.
   - **Container memif connections** - VPP memif virtual interface tests to
     interconnect VPP instances with L2XC and L2BD.
     number of users and ports per user.
   - **Container memif connections** - VPP memif virtual interface tests to
     interconnect VPP instances with L2XC and L2BD.

-  - **Container Orchestrated Topologies** - Container topologies connected over
+  - **Container K8s Orchestrated Topologies** - Container topologies connected over

     the memif virtual interface.
 
 - 2port40GE XL710 Intel
     the memif virtual interface.
 
 - 2port40GE XL710 Intel