FIX: Report - DPDK static content

Change-Id: If233133bfaf01cb46979ee83b4704b2645a8b7e2
Signed-off-by: Tibor Frank <tifrank@cisco.com>

5 files changed, 16 insertions, 16 deletions

diff --git a/docs/report/dpdk_performance_tests/overview.rst b/docs/report/dpdk_performance_tests/overview.rst
index e6abb53c90..81f5ed5efc 100644
--- a/docs/report/dpdk_performance_tests/overview.rst
+++ b/docs/report/dpdk_performance_tests/overview.rst
@@ -10,8 +10,8 @@ Logical Topologies
 ------------------
 
 CSIT DPDK performance tests are executed on physical testbeds described
-in :ref:`tested_physical_topologies`. Based on the packet path thru
-server SUTs, three distinct logical topology types are used for DPDK DUT
+in :ref:`tested_physical_topologies`. Based on the packet path through
+server SUTs, one distinct logical topology type is used for DPDK DUT
 data plane testing:
 
 #. NIC-to-NIC switching topologies.
diff --git a/docs/report/dpdk_performance_tests/packet_latency_graphs/index.rst b/docs/report/dpdk_performance_tests/packet_latency_graphs/index.rst
index 43f557c517..1604fb1576 100644
--- a/docs/report/dpdk_performance_tests/packet_latency_graphs/index.rst
+++ b/docs/report/dpdk_performance_tests/packet_latency_graphs/index.rst
@@ -5,14 +5,14 @@ Plotted results are generated from a single execution of CSIT NDR discovery
 test. Box plots are used to show the Minimum, Median and Maximum packet
 latency per test.
 
-*Title of each graph* is a regex (regular expression) matching all
-throughput test cases plotted on this graph, *X-axis labels* are indices
-of individual test suites executed by
-FD.io test executor dpdk performance jobs that created result output file
-used as data source for the graph, *Y-axis labels* are measured packet Latency
-[uSec] values, and the *Graph legend* lists the plotted test suites and their
-indices. Latency is reported for concurrent symmetric bi-directional flows,
-separately for each direction: i) West-to-East:
+*Title of each graph* describes the packet path, testbed topology, processor
+architecture, packet size, number of cores and threads used by workers and
+DUT configuration, *X-axis labels* are indices of individual test suites
+executed by FD.io test executor dpdk performance jobs that created result output
+file used as data source for the graph, *Y-axis labels* are measured packet
+Latency [uSec] values, and the *Graph legend* lists the plotted test suites and
+their indices. Latency is reported for concurrent symmetric bi-directional
+flows, separately for each direction: i) West-to-East:
 TGint1-to-SUT1-to-SUT2-to-TGint2, and ii) East-to-West:
 TGint2-to-SUT2-to-SUT1-to-TGint1.
 
diff --git a/docs/report/dpdk_performance_tests/packet_latency_graphs/ip4.rst b/docs/report/dpdk_performance_tests/packet_latency_graphs/ip4.rst
index 819e4a9ebd..21ddba1c9b 100644
--- a/docs/report/dpdk_performance_tests/packet_latency_graphs/ip4.rst
+++ b/docs/report/dpdk_performance_tests/packet_latency_graphs/ip4.rst
@@ -2,7 +2,7 @@ L3fwd
 =====
 
 This section includes summary graphs of L3FWD Phy-to-Phy performance with packet
-routed forwarding measured at 50% of discovered NDR throughput rate. Latency is
+routed forwarding measured at 100% of discovered NDR throughput rate. Latency is
 reported for L3FWD running in multiple configurations of L3FWD pmd thread(s),
 a.k.a. L3FWD data plane thread(s), and their physical CPU core(s) placement.
 
diff --git a/docs/report/dpdk_performance_tests/packet_latency_graphs/l2.rst b/docs/report/dpdk_performance_tests/packet_latency_graphs/l2.rst
index 6d7ea30c98..c07c35d458 100644
--- a/docs/report/dpdk_performance_tests/packet_latency_graphs/l2.rst
+++ b/docs/report/dpdk_performance_tests/packet_latency_graphs/l2.rst
@@ -2,7 +2,7 @@ Testpmd
 =======
 
 This section includes summary graphs of Testpmd Phy-to-Phy packet
-latency with L2 Ethernet Interface Loop measured at 50% of discovered
+latency with L2 Ethernet Interface Loop measured at 100% of discovered
 NDR throughput rate. Latency is reported for Testpmd running in multiple
 configurations of Testpmd pmd thread(s), a.k.a. Testpmd data plane
 thread(s), and their physical CPU core(s) placement.
diff --git a/docs/report/dpdk_performance_tests/packet_throughput_graphs/index.rst b/docs/report/dpdk_performance_tests/packet_throughput_graphs/index.rst
index cfa75419e6..5274e6be9a 100644
--- a/docs/report/dpdk_performance_tests/packet_throughput_graphs/index.rst
+++ b/docs/report/dpdk_performance_tests/packet_throughput_graphs/index.rst
@@ -17,10 +17,10 @@ top edge of the box. If multiple samples match only two values, and all
 samples fall between them, then no whiskers are plotted. If all samples
 have the same value, only a horizontal line is plotted.
 
-*Title of each graph* is a regex (regular expression) matching all
-throughput test cases plotted on this graph, *X-axis labels* are indices
-of individual test suites executed by
-FD.io test executor dpdk performance jobs that created result output
+*Title of each graph* describes the packet path, testbed topology, processor
+architecture, packet size, number of cores and threads used by workers and
+DUT configuration, *X-axis labels* are indices by individual test suites
+executed by FD.io test executor dpdk performance jobs that created result output
 files used as data sources for the graph, *Y-axis labels* are measured Packets
 Per Second [pps] values, and the *Graph legend* lists the plotted test suites
 and their indices.