From bbfcee8d3cf51ec01d269245970ef41bb072c580 Mon Sep 17 00:00:00 2001 From: Vratko Polak Date: Wed, 13 Feb 2019 09:46:34 +0100 Subject: Apply minor improvements to methodology docs Change-Id: Ice5625c2b04dce174b19748b0ccccdf813b66f2a Signed-off-by: Vratko Polak --- docs/report/introduction/methodology_multi_core_speedup.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/report/introduction/methodology_multi_core_speedup.rst') diff --git a/docs/report/introduction/methodology_multi_core_speedup.rst b/docs/report/introduction/methodology_multi_core_speedup.rst index 94840406a1..b42bf42f92 100644 --- a/docs/report/introduction/methodology_multi_core_speedup.rst +++ b/docs/report/introduction/methodology_multi_core_speedup.rst @@ -51,7 +51,7 @@ In all CSIT tests care is taken to ensure that each VPP worker handles the same amount of received packet load and does the same amount of packet processing work. This is achieved by evenly distributing per interface type (e.g. physical, virtual) receive queues over VPP workers -using default VPP round- robin mapping and by loading these queues with +using default VPP round-robin mapping and by loading these queues with the same amount of packet flows. If number of VPP workers is higher than number of physical or virtual @@ -62,5 +62,5 @@ for virtual interfaces are used for this purpose. Section :ref:`throughput_speedup_multi_core` includes a set of graphs illustrating packet throughout speedup when running VPP worker threads on multiple cores. Note that in quite a few test cases running VPP -workers on 2 or 4 physical cores hits the I/O bandwidth or packets-per- -second limit of tested NIC. +workers on 2 or 4 physical cores hits the I/O bandwidth +or packets-per-second limit of tested NIC. -- cgit 1.2.3-korg