CSIT-618 Release report update VIII

Change-Id: Idec390861aa5ac8a1a485d5996fbfef444ac8a29
Signed-off-by: Peter Mikus <pmikus@cisco.com>

3 files changed, 16 insertions, 14 deletions

diff --git a/docs/report/vpp_performance_tests/csit_release_notes.rst b/docs/report/vpp_performance_tests/csit_release_notes.rst
index 3daff961b4..0ee3e82f59 100644
--- a/docs/report/vpp_performance_tests/csit_release_notes.rst
+++ b/docs/report/vpp_performance_tests/csit_release_notes.rst
@@ -31,8 +31,8 @@ Changes in CSIT |release|
      on CSIT wiki page

      `Design_Optimizations <https://wiki.fd.io/view/CSIT/Design_Optimizations>`_.

 

-   - For more detail see the CSIT Framework Design section in this

-     report;

+   - For more detail see the :ref:`CSIT Framework Design <csit-design>` section

+     in this report;

 

 #. Changes to CSIT driver for TRex Traffic Generator:

 

@@ -155,27 +155,27 @@ Here is the list of known issues in CSIT |release| for VPP performance tests:
 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+

 | # | Issue                                           | Jira ID    | Description                                                     |

 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+

-| 1 | Security-groups acl-plugin scale tests failure  | CSIT-xxx   | VPP with 2 worker threads crashes during security-groups        |

+| 1 | Security-groups acl-plugin scale tests failure  | CSIT-731   | VPP with 2 worker threads crashes during security-groups        |

 |   | with stateful acls if VPP with 2 worker threads | VPP-912    | iaclNsf and oaclNsf tests with 100k flows.                      |

 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+

-| 2 | VPP fails memif tests in 4 worker 2 core setup  | CSIT-xxx   | VPP with 4 worker threads running on 2 physical cores crashes   |

-|   |                                                 | VPP-xxx    | during memif tests. Initial debugging points to DPDK code       |

+| 2 | VPP fails memif tests in 4 worker 2 core setup  | CSIT-732   | VPP with 4 worker threads running on 2 physical cores crashes   |

+|   |                                                 | VPP-920    | during memif tests. Initial debugging points to DPDK code       |

 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+

-| X | NDR discovery test failures 1518B frame size    | VPP-663    | VPP reporting errors: dpdk-input Rx ip checksum errors.         |

+| 3 | NDR discovery test failures 1518B frame size    | VPP-663    | VPP reporting errors: dpdk-input Rx ip checksum errors.         |

 |   | for ip4scale200k, ip4scale2m scale IPv4 routed- |            | Observed frequency: all test runs.                              |

 |   | forwarding tests. ip4scale20k tests are fine.   |            |                                                                 |

 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+

-| X | Vic1385 and Vic1227 low performance.            | VPP-664    | Low NDR performance.                                            |

+| 4 | Vic1385 and Vic1227 low performance.            | VPP-664    | Low NDR performance.                                            |

 |   |                                                 |            |                                                                 |

 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+

-| X | Sporadic NDR discovery test failures on x520.   | CSIT-750   | Suspected issue with HW settings (BIOS, FW) in LF               |

+| 5 | Sporadic NDR discovery test failures on x520.   | CSIT-750   | Suspected issue with HW settings (BIOS, FW) in LF               |

 |   |                                                 |            | infrastructure. Issue can't be replicated outside LF.           |

 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+

-| X | VPP in 2t2c setups - large variation            | CSIT-568   | Suspected NIC firmware or DPDK driver issue affecting NDR       |

+| 6 | VPP in 2t2c setups - large variation            | CSIT-568   | Suspected NIC firmware or DPDK driver issue affecting NDR       |

 |   | of discovered NDR throughput values across      |            | throughput. Applies to XL710 and X710 NICs, x520 NICs are fine. |

 |   | multiple test runs with xl710 and x710 NICs.    |            |                                                                 |

 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+

-| X | Lower than expected NDR and PDR throughput with | CSIT-569   | Suspected NIC firmware or DPDK driver issue affecting NDR and   |

+| 7 | Lower than expected NDR and PDR throughput with | CSIT-569   | Suspected NIC firmware or DPDK driver issue affecting NDR and   |

 |   | xl710 and x710 NICs, compared to x520 NICs.     |            | PDR throughput. Applies to XL710 and X710 NICs.                 |

 +---+-------------------------------------------------+------------+-----------------------------------------------------------------+

 

diff --git a/docs/report/vpp_performance_tests/overview.rst b/docs/report/vpp_performance_tests/overview.rst
index 98a4d06681..5cf7b1d355 100644
--- a/docs/report/vpp_performance_tests/overview.rst
+++ b/docs/report/vpp_performance_tests/overview.rst
@@ -361,8 +361,9 @@ TRex is installed and run on the TG compute node. The typical procedure is:
 
   $ sh -c 'cd /opt/trex-core-2.25/scripts/ && sudo nohup ./t-rex-64 -i -c 7 --iom 0 > /dev/null 2>&1 &' > /dev/null
 
-- There are traffic streams dynamically prepared for each test. The traffic
-  is sent and the statistics obtained using trex_stl_lib.api.STLClient.
+- There are traffic streams dynamically prepared for each test, based on traffic
+  profiles. The traffic is sent and the statistics obtained using
+  trex_stl_lib.api.STLClient.
 
 **Measuring packet loss**
 
diff --git a/docs/report/vpp_performance_tests/test_environment.rst b/docs/report/vpp_performance_tests/test_environment.rst
index 9392259a97..20ea77f31a 100644
--- a/docs/report/vpp_performance_tests/test_environment.rst
+++ b/docs/report/vpp_performance_tests/test_environment.rst
@@ -251,7 +251,8 @@ Below a subset of the running configuration:
 

 - **isolcpus=<cpu number>-<cpu number>** used for all cpu cores apart from

   first core of each socket used for running VPP worker threads and Qemu/LXC

-  processes https://www.kernel.org/doc/Documentation/kernel-parameters.txt

+  processes

+  https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt

 - **intel_pstate=disable** - [X86] Do not enable intel_pstate as the default

   scaling driver for the supported processors. Intel P-State driver decide what

   P-state (CPU core power state) to use based on requesting policy from the

@@ -269,7 +270,7 @@ Below a subset of the running configuration:
 - **rcu_nocbs** - [KNL] In kernels built with CONFIG_RCU_NOCB_CPU=y, set the

   specified list of CPUs to be no-callback CPUs, that never queue RCU callbacks

   (read-copy update).

-  https://www.kernel.org/doc/Documentation/kernel-parameters.txt

+  https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt

 

 **Applied command line boot parameters:**