* [dts] [PATCH V3 1/3] add test plan for performance thread test suite
@ 2018-10-18 15:38 Wang Fei
2018-10-19 3:07 ` Tu, Lijuan
0 siblings, 1 reply; 2+ messages in thread
From: Wang Fei @ 2018-10-18 15:38 UTC (permalink / raw)
To: dts; +Cc: lijuan.tu, wang fei
From: wang fei <feix.y.wang@intel.com>
Signed-off-by: wang fei <feix.y.wang@intel.com>
---
test_plans/performance_thread_test_plan.rst | 280 ++++++++++++++++++++
1 file changed, 280 insertions(+)
create mode 100644 test_plans/performance_thread_test_plan.rst
diff --git a/test_plans/performance_thread_test_plan.rst b/test_plans/performance_thread_test_plan.rst
new file mode 100644
index 0000000..09d64a3
--- /dev/null
+++ b/test_plans/performance_thread_test_plan.rst
@@ -0,0 +1,280 @@
+.. Copyright (c) <2011-2017>, Intel Corporation
+ All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+
+ - Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+
+ - Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in
+ the documentation and/or other materials provided with the
+ distribution.
+
+ - Neither the name of Intel Corporation nor the names of its
+ contributors may be used to endorse or promote products derived
+ from this software without specific prior written permission.
+
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+ "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+ FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+ COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+ (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+ SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+ STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+ OF THE POSSIBILITY OF SUCH DAMAGE.
+
+======================================
+Performance-thread performance Tests
+======================================
+
+The Performance-Thread results are produced using ``l3fwd-thread`` application.
+
+For more information about Performance Thread sameple applicaton please refer to
+link: http://doc.dpdk.org/guides/sample_app_ug/performance_thread.html
+
+Prerequisites
+==============
+
+1. Hardware requirements:
+
+ - For each CPU socket, each memory channel should be populated with at least 1x DIMM
+ - Board is populated with 4x 1GbE or 10GbE ports. Special PCIe restrictions may
+ be required for performance. For example, the following requirements should be
+ met for Intel 82599 (Niantic) NICs:
+
+ - NICs are plugged into PCIe Gen2 or Gen3 slots
+ - For PCIe Gen2 slots, the number of lanes should be 8x or higher
+ - A single port from each NIC should be used, so for 4x ports, 4x NICs should
+ be used
+
+ - NIC ports connected to traffic generator. It is assumed that the NIC ports
+ P0, P1 (as identified by the DPDK application) are connected to the
+ traffic generator ports TG0, TG1. The application-side port mask of
+ NIC ports P0, P1 is noted as PORTMASK in this section.
+
+2. BIOS requirements:
+
+ - Intel Hyper-Threading Technology is ENABLED
+ - Hardware Prefetcher is DISABLED
+ - Adjacent Cache Line Prefetch is DISABLED
+ - Direct Cache Access is DISABLED
+
+3. Linux kernel requirements:
+
+ - Linux kernel has the following features enabled: huge page support, UIO, HPET
+ - Appropriate number of huge pages are reserved at kernel boot time
+ - The IDs of the hardware threads (logical cores) per each CPU socket can be
+ determined by parsing the file /proc/cpuinfo. The naming convention for the
+ logical cores is: C{x.y.z} = hyper-thread z of physical core y of CPU socket x,
+ with typical values of x = 0 .. 3, y = 0 .. 7, z = 0 .. 1. Logical cores
+ C{0.0.1} and C{0.0.1} should be avoided while executing the test, as they are
+ used by the Linux kernel for running regular processes.
+
+4. Software application requirements
+
+5. If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When
+ using vfio, use the following commands to to load the vfio driver and bind it
+ to the device under test::
+
+ modprobe vfio
+ modprobe vfio-pci
+ usertools/dpdk-devbind.py --bind=vfio-pci device_bus_id
+
+6. Build dpdk and performance thread sample app
+ -> make install RTE_SDK=`pwd` T=x86_64-native-linuxapp-gcc
+ -> make -C examples/performance-thread RTE_SDK=`pwd` T=x86_64-native-linuxapp-gcc
+
+7. Bind two ports to igb_uio driver and connect these two ports with two ixia ports
+ -> ./usertools/dpdk-devbind.py --bind=igb_uio 0000:18:00.0 0000:1a:00.0
+
+
+Detail test cases and test steps
+=================================
+
+Test Case: one_lcore_per_pcore performance::
+
+ 1: Launch app:
+ ./examples/performance-thread/l3fwd-thread/x86_64-native-linuxapp-gcc/l3fwd-thread \
+ -c ff -n 2 -- -P -p 3 \
+ --enable-jumbo --max-pkt-len 2500 \
+ --rx="(0,0,0,0)(1,0,0,0)" \
+ --tx="(1,0)" \
+ --no-lthread
+ ( Note: option "--stat-lcore" is not enabled in the automation scripts)
+
+ 2: Send traffic(see traffic config below) and verify performance
+
+ 3: Repeat above tests with below command lines respectively
+
++-----+-----------------------------------------------------------------------------------------------------------+
+| # | Command Line |
++-----+-----------------------------------------------------------------------------------------------------------+
+|1 |./l3fwd-thread -c ff -n 2 -- -P -p 3 --enable-jumbo --max-pkt-len 2500 \ |
+| | --rx="(0,0,0,0)(1,0,1,1) --tx="(2,0)(3,1) \ |
+| | --no-lthread |
++-----+-----------------------------------------------------------------------------------------------------------+
+|2 |./l3fwd-thread -c ff -n 2 -- -P -p 3 --enable-jumbo --max-pkt-len 2500 \ |
+| | --rx="(0,0,0,0)(0,1,1,1)(1,0,2,2)(1,1,3,3)" \ |
+| | --tx="(4,0)(5,1)(6,2)(7,3)" --no-lthread |
++-----+-----------------------------------------------------------------------------------------------------------+
+|3 |./l3fwd-thread -c ff -n 2 -- -P -p 3 --enable-jumbo --max-pkt-len 2500 \ |
+| | --rx="(0,0,0,0)(0,1,1,1)(0,2,2,2)(0,3,3,3)(1,0,4,4)(1,1,5,5)(1,2,6,6)(1,3,7,7)" \ |
+| | --tx="(8,0)(9,1)(10,2)(11,3)(12,4)(13,5)(14,6)(15,7)" \ |
+| | --no-lthread |
++-----+-----------------------------------------------------------------------------------------------------------|
+
+ 4: Check test results output as below table
+
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Cores | Fsize | Unidirectional MPPS | Line Rate(%) | Bidirectional MPPS | Line Rate(%) |
++=======+=======+=====================+==============+====================+==============+
+| Core N| 64 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 128 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 256 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 512 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 1024 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 2000 | | | | |
+-----------------------------------------------------------------------------------------+
+
+
+Test Case: n_lcore_per_pcore performance::
+
+ 1: Launch app:
+ ./examples/performance-thread/l3fwd-thread/x86_64-native-linuxapp-gcc/l3fwd-thread \
+ --lcores="2,(0-1)@0" -- -P -p 3 \
+ --enable-jumbo --max-pkt-len 2500 \
+ --rx="(0,0,0,0)(1,0,0,0)" \
+ --tx="(1,0)"
+ ( Note: option "--stat-lcore" is not enabled in the automation scripts)
+
+ 2: Send traffic(see traffic config below) and verify performance both directional and bi-directional
+
+ 3: Repeat above tests with below command lines respectively
+
++-----+-----------------------------------------------------------------------------------------------------------+
+| # | Command Line |
++-----+-----------------------------------------------------------------------------------------------------------+
+|1 |./l3fwd-thread -n 2 --lcores="(0-3)@0,4" -- -P -p 3 \ |
+| | --enable-jumbo --max-pkt-len 2500 \ |
+| | --rx="(0,0,0,0)(1,0,1,1)" \ |
+| | --tx="(2,0)(3,1)" \ |
+| | --no-lthread |
++-----+-----------------------------------------------------------------------------------------------------------+
+|2 |./l3fwd-thread -n 2 --lcores="(0-7)@0,8" -- -P -p 3 \ |
+| | --enable-jumbo --max-pkt-len 2500 \ |
+| | --rx="(0,0,0,0)(0,1,1,1)(1,0,2,2)(1,1,3,3)" \ |
+| | --tx="(4,0)(5,1)(6,2)(7,3)" \ |
+| | --no-lthread |
++-----+-----------------------------------------------------------------------------------------------------------+
+|3 |./l3fwd-thread -n 2 --lcores="(0-15)@0,16" -- -P -p 3 \ |
+| | --enable-jumbo --max-pkt-len 2500 \ |
+| | --rx="(0,0,0,0)(0,1,1,1)(0,2,2,2)(0,3,3,3)(1,0,4,4)(1,1,5,5)(1,2,6,6)(1,3,7,7)" \ |
+| | --tx="(8,0)(9,1)(10,2)(11,3)(12,4)(13,5)(14,6)(15,7)" \ |
+| | --no-lthread |
++-----+-----------------------------------------------------------------------------------------------------------|
+
+ 4: Check test results output as below table:
+
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Cores | Fsize | Unidirectional MPPS | Line Rate(%) | Bidirectional MPPS | Line Rate(%) |
++=======+=======+=====================+==============+====================+==============+
+| Core N| 64 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 128 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 256 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 512 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 1024 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 2000 | | | | |
+-----------------------------------------------------------------------------------------+
+
+
+
+
+Test Case: n_lthread_per_pcore performance::
+
+ 1: Launch app:
+ ./examples/performance-thread/l3fwd-thread/x86_64-native-linuxapp-gcc/l3fwd-thread \
+ -c ff -n 2 -- -P -p 3 \
+ --enable-jumbo --max-pkt-len 2500 \
+ ----tx="(0,0)" \
+ --tx="(0,0)"
+ ( Note: option "--stat-lcore" is not enabled in the automation scripts)
+
+ 2: Send traffic(see traffic config below) and verify performance both directional and bi-directional
+
+ 3: Repeat above tests with below command lines respectively
+
++-----+-----------------------------------------------------------------------------------------------------------+
+| # | Command Line |
++-----+-----------------------------------------------------------------------------------------------------------+
+|1 |./l3fwd-thread -c ff -n 2 -- -P -p 3 \ |
+| | --enable-jumbo --max-pkt-len 2500 \ |
+| | --rx="(0,0,0,0)(1,0,0,1)" \ |
+| | --tx="(0,0)(0,1)" \ |
++-----+-----------------------------------------------------------------------------------------------------------+
+|2 |./l3fwd-thread -c ff -n 2 -- -P -p 3 \ |
+| | --enable-jumbo --max-pkt-len 2500 \ |
+| | --rx="(0,0,0,0)(0,1,0,1)(1,0,0,2)(1,1,0,3)" \ |
+| | --tx="(0,0)(0,1)(0,2)(0,3)" \ |
++-----+-----------------------------------------------------------------------------------------------------------+
+|3 |./l3fwd-thread -c ff -n 2 -- -P -p 3 \ |
+| | --enable-jumbo --max-pkt-len 2500 \ |
+| | --rx="(0,0,0,0)(0,1,0,1)(0,2,0,2)(0,3,0,3)(1,0,0,4)(1,1,0,5)(1,2,0,6)(1,3,0,7)" \ |
+| | --tx="(0,0)(0,1)(0,2)(0,3)(0,4)(0,5)(0,6)(0,7)" \ |
++-----+-----------------------------------------------------------------------------------------------------------|
+
+ 4: Check test results output as below table:
+
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Cores | Fsize | Unidirectional MPPS | Line Rate(%) | Bidirectional MPPS | Line Rate(%) |
++=======+=======+=====================+==============+====================+==============+
+| Core N| 64 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 128 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 256 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 512 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 1024 | | | | |
++-------+-------+---------------------+--------------+--------------------+--------------+
+| Core N| 2000 | | | | |
+-----------------------------------------------------------------------------------------+
+
+
+
+How to configure Traffic generator to send traffic:
+=====================================================
+
+The flows need to be configured and started by the traffic generator:
+
+|
+
++------+---------+------------+---------------+------------+---------+
+| Flow | Traffic | MAC | MAC | IPV4 | IPV4 |
+| | Gen. | Src. | Dst. | Src. | Dest. |
+| | Port | Address | Address | Address | Address |
++------+---------+------------+---------------+------------+---------+
+| 1 | TG0 | Random MAC | DUT Port0 Mac | Random IP | 2.1.1.1 |
++------+---------+------------+---------------+------------+---------+
+| 2 | TG1 | Random Mac | DUT port1 Mac | Random IP | 1.1.1.1 |
++------+---------+------------+---------------+------------+---------+
+
+|
+Frame sizes should be configured from 64,128,256,512,1024,2000, etc
--
2.17.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dts] [PATCH V3 1/3] add test plan for performance thread test suite
2018-10-18 15:38 [dts] [PATCH V3 1/3] add test plan for performance thread test suite Wang Fei
@ 2018-10-19 3:07 ` Tu, Lijuan
0 siblings, 0 replies; 2+ messages in thread
From: Tu, Lijuan @ 2018-10-19 3:07 UTC (permalink / raw)
To: Wang, FeiX Y, dts
Comments inline.
> -----Original Message-----
> From: Wang, FeiX Y
> Sent: Thursday, October 18, 2018 11:39 PM
> To: dts@dpdk.org
> Cc: Tu, Lijuan <lijuan.tu@intel.com>; Wang, FeiX Y <feix.y.wang@intel.com>
> Subject: [dts] [PATCH V3 1/3] add test plan for performance thread test suite
>
> From: wang fei <feix.y.wang@intel.com>
>
> Signed-off-by: wang fei <feix.y.wang@intel.com>
> ---
> test_plans/performance_thread_test_plan.rst | 280
> ++++++++++++++++++++
> 1 file changed, 280 insertions(+)
> create mode 100644 test_plans/performance_thread_test_plan.rst
>
> diff --git a/test_plans/performance_thread_test_plan.rst
> b/test_plans/performance_thread_test_plan.rst
> new file mode 100644
> index 0000000..09d64a3
> --- /dev/null
> +++ b/test_plans/performance_thread_test_plan.rst
> @@ -0,0 +1,280 @@
> +.. Copyright (c) <2011-2017>, Intel Corporation
> + All rights reserved.
> +
> + Redistribution and use in source and binary forms, with or without
> + modification, are permitted provided that the following conditions
> + are met:
> +
> + - Redistributions of source code must retain the above copyright
> + notice, this list of conditions and the following disclaimer.
> +
> + - Redistributions in binary form must reproduce the above copyright
> + notice, this list of conditions and the following disclaimer in
> + the documentation and/or other materials provided with the
> + distribution.
> +
> + - Neither the name of Intel Corporation nor the names of its
> + contributors may be used to endorse or promote products derived
> + from this software without specific prior written permission.
> +
> + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
> CONTRIBUTORS
> + "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
> NOT
> + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
> FITNESS
> + FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
> THE
> + COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
> INDIRECT,
> + INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> + (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
> GOODS OR
> + SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
> INTERRUPTION)
> + HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
> CONTRACT,
> + STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> + ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
> ADVISED
> + OF THE POSSIBILITY OF SUCH DAMAGE.
> +
> +======================================
> +Performance-thread performance Tests
> +======================================
> +
> +The Performance-Thread results are produced using ``l3fwd-thread``
> application.
> +[Lijuan] could you add an introduction here, it is also ok that an abstract from the dpdk document.
> +For more information about Performance Thread sameple applicaton
> please refer to
> +link:
> http://doc.dpdk.org/guides/sample_app_ug/performance_thread.html
> +
> +Prerequisites
> +==============
> +
> +1. Hardware requirements:
> +
> + - For each CPU socket, each memory channel should be populated
> with at least 1x DIMM
> + - Board is populated with 4x 1GbE or 10GbE ports. Special PCIe
> restrictions may
> + be required for performance. For example, the following
> requirements should be
> + met for Intel 82599 (Niantic) NICs:
> +
> + - NICs are plugged into PCIe Gen2 or Gen3 slots
> + - For PCIe Gen2 slots, the number of lanes should be 8x or higher
> + - A single port from each NIC should be used, so for 4x ports, 4x
> NICs should
> + be used
> +
> + - NIC ports connected to traffic generator. It is assumed that the NIC
> ports
> + P0, P1 (as identified by the DPDK application) are connected to the
> + traffic generator ports TG0, TG1. The application-side port mask of
> + NIC ports P0, P1 is noted as PORTMASK in this section.
> +
> +2. BIOS requirements:
> +
> + - Intel Hyper-Threading Technology is ENABLED
> + - Hardware Prefetcher is DISABLED
> + - Adjacent Cache Line Prefetch is DISABLED
> + - Direct Cache Access is DISABLED
> +
> +3. Linux kernel requirements:
> +
> + - Linux kernel has the following features enabled: huge page support,
> UIO, HPET
> + - Appropriate number of huge pages are reserved at kernel boot time
> + - The IDs of the hardware threads (logical cores) per each CPU socket
> can be
> + determined by parsing the file /proc/cpuinfo. The naming
> convention for the
> + logical cores is: C{x.y.z} = hyper-thread z of physical core y of CPU
> socket x,
> + with typical values of x = 0 .. 3, y = 0 .. 7, z = 0 .. 1. Logical cores
> + C{0.0.1} and C{0.0.1} should be avoided while executing the test, as
> they are
> + used by the Linux kernel for running regular processes.
> +
> +4. Software application requirements
> +
> +5. If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in
> bios.When
> + using vfio, use the following commands to to load the vfio driver and
> bind it
> + to the device under test::
> +
> + modprobe vfio
> + modprobe vfio-pci
> + usertools/dpdk-devbind.py --bind=vfio-pci device_bus_id
> +
> +6. Build dpdk and performance thread sample app
> + -> make install RTE_SDK=`pwd` T=x86_64-native-linuxapp-gcc
> + -> make -C examples/performance-thread RTE_SDK=`pwd`
> T=x86_64-native-linuxapp-gcc
> +
> +7. Bind two ports to igb_uio driver and connect these two ports with two
> ixia ports
> + -> ./usertools/dpdk-devbind.py --bind=igb_uio 0000:18:00.0
> 0000:1a:00.0
> +
> +
> +Detail test cases and test steps
> +=================================
[Lijuan] could you clarify the arguments closely to the feature, such as lcore, rx tx no-lthread, and how to choose the values, for example , why is "--rx="(0,0,0,0)(1,0,1,1) --tx="(2,0)(3,1)"
> +
> +Test Case: one_lcore_per_pcore performance::
> +
> + 1: Launch app:
> + ./examples/performance-thread/l3fwd-thread/x86_64-native-linu
> xapp-gcc/l3fwd-thread \
> + -c ff -n 2 -- -P -p 3 \
> + --enable-jumbo --max-pkt-len 2500 \
> + --rx="(0,0,0,0)(1,0,0,0)" \
> + --tx="(1,0)" \
> + --no-lthread
> + ( Note: option "--stat-lcore" is not enabled in the automation
> scripts)
> +
> + 2: Send traffic(see traffic config below) and verify performance
> +
> + 3: Repeat above tests with below command lines respectively
> +
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +| # | Command Line
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +|1 |./l3fwd-thread -c ff -n 2 -- -P -p 3 --enable-jumbo --max-pkt-len
> 2500 \ |
> +| | --rx="(0,0,0,0)(1,0,1,1) --tx="(2,0)(3,1) \
> |
> +| | --no-lthread
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +|2 |./l3fwd-thread -c ff -n 2 -- -P -p 3 --enable-jumbo --max-pkt-len
> 2500 \ |
> +| | --rx="(0,0,0,0)(0,1,1,1)(1,0,2,2)(1,1,3,3)" \
> |
> +| | --tx="(4,0)(5,1)(6,2)(7,3)" --no-lthread
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +|3 |./l3fwd-thread -c ff -n 2 -- -P -p 3 --enable-jumbo --max-pkt-len
> 2500 \ |
> +| |
> --rx="(0,0,0,0)(0,1,1,1)(0,2,2,2)(0,3,3,3)(1,0,4,4)(1,1,5,5)(1,2,6,6)(1,3,7,7)" \
> |
> +| |
> --tx="(8,0)(9,1)(10,2)(11,3)(12,4)(13,5)(14,6)(15,7)" \
> |
> +| | --no-lthread
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------|
> +
> + 4: Check test results output as below table
> +
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Cores | Fsize | Unidirectional MPPS | Line Rate(%) | Bidirectional MPPS |
> Line Rate(%) |
> ++=======+=======+=====================+==============+=======
> =============+==============+
> +| Core N| 64 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 128 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 256 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 512 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 1024 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 2000 | | |
> | |
> +-----------------------------------------------------------------------------------------+
> +
> +
> +Test Case: n_lcore_per_pcore performance::
> +
> + 1: Launch app:
> + ./examples/performance-thread/l3fwd-thread/x86_64-native-linu
> xapp-gcc/l3fwd-thread \
> + --lcores="2,(0-1)@0" -- -P -p 3 \
> + --enable-jumbo --max-pkt-len 2500 \
> + --rx="(0,0,0,0)(1,0,0,0)" \
> + --tx="(1,0)"
> + ( Note: option "--stat-lcore" is not enabled in the automation
> scripts)
> +
> + 2: Send traffic(see traffic config below) and verify performance both
> directional and bi-directional
> +
> + 3: Repeat above tests with below command lines respectively
> +
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +| # | Command Line
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +|1 |./l3fwd-thread -n 2 --lcores="(0-3)@0,4" -- -P -p 3 \
> |
> +| | --enable-jumbo --max-pkt-len 2500 \
> |
> +| | --rx="(0,0,0,0)(1,0,1,1)" \
> |
> +| | --tx="(2,0)(3,1)" \
> |
> +| | --no-lthread
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +|2 |./l3fwd-thread -n 2 --lcores="(0-7)@0,8" -- -P -p 3 \
> |
> +| | --enable-jumbo --max-pkt-len 2500 \
> |
> +| | --rx="(0,0,0,0)(0,1,1,1)(1,0,2,2)(1,1,3,3)" \
> |
> +| | --tx="(4,0)(5,1)(6,2)(7,3)" \
> |
> +| | --no-lthread
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +|3 |./l3fwd-thread -n 2 --lcores="(0-15)@0,16" -- -P -p 3 \
> |
> +| | --enable-jumbo --max-pkt-len 2500 \
> |
> +| |
> --rx="(0,0,0,0)(0,1,1,1)(0,2,2,2)(0,3,3,3)(1,0,4,4)(1,1,5,5)(1,2,6,6)(1,3,7,7)" \
> |
> +| |
> --tx="(8,0)(9,1)(10,2)(11,3)(12,4)(13,5)(14,6)(15,7)" \
> |
> +| | --no-lthread
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------|
> +
> + 4: Check test results output as below table:
> +
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Cores | Fsize | Unidirectional MPPS | Line Rate(%) | Bidirectional MPPS |
> Line Rate(%) |
> ++=======+=======+=====================+==============+=======
> =============+==============+
> +| Core N| 64 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 128 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 256 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 512 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 1024 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 2000 | | |
> | |
> +-----------------------------------------------------------------------------------------+
> +
> +
> +
> +
> +Test Case: n_lthread_per_pcore performance::
> +
> + 1: Launch app:
> + ./examples/performance-thread/l3fwd-thread/x86_64-native-lin
> uxapp-gcc/l3fwd-thread \
> + -c ff -n 2 -- -P -p 3 \
> + --enable-jumbo --max-pkt-len 2500 \
> + ----tx="(0,0)" \
> + --tx="(0,0)"
> + ( Note: option "--stat-lcore" is not enabled in the automation
> scripts)
> +
> + 2: Send traffic(see traffic config below) and verify performance both
> directional and bi-directional
> +
> + 3: Repeat above tests with below command lines respectively
> +
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +| # | Command Line
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +|1 |./l3fwd-thread -c ff -n 2 -- -P -p 3 \
> |
> +| | --enable-jumbo --max-pkt-len 2500 \
> |
> +| | --rx="(0,0,0,0)(1,0,0,1)" \
> |
> +| | --tx="(0,0)(0,1)" \
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +|2 |./l3fwd-thread -c ff -n 2 -- -P -p 3 \
> |
> +| | --enable-jumbo --max-pkt-len 2500 \
> |
> +| | --rx="(0,0,0,0)(0,1,0,1)(1,0,0,2)(1,1,0,3)" \
> |
> +| | --tx="(0,0)(0,1)(0,2)(0,3)" \
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------+
> +|3 |./l3fwd-thread -c ff -n 2 -- -P -p 3 \
> |
> +| | --enable-jumbo --max-pkt-len 2500 \
> |
> +| |
> --rx="(0,0,0,0)(0,1,0,1)(0,2,0,2)(0,3,0,3)(1,0,0,4)(1,1,0,5)(1,2,0,6)(1,3,0,7)" \
> |
> +| | --tx="(0,0)(0,1)(0,2)(0,3)(0,4)(0,5)(0,6)(0,7)" \
> |
> ++-----+------------------------------------------------------------------------------------
> -----------------------|
> +
> + 4: Check test results output as below table:
> +
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Cores | Fsize | Unidirectional MPPS | Line Rate(%) | Bidirectional MPPS |
> Line Rate(%) |
> ++=======+=======+=====================+==============+=======
> =============+==============+
> +| Core N| 64 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 128 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 256 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 512 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 1024 | | |
> | |
> ++-------+-------+---------------------+--------------+--------------------+--------------
> +
> +| Core N| 2000 | | |
> | |
> +-----------------------------------------------------------------------------------------+
> +
> +
> +
> +How to configure Traffic generator to send traffic:
> +=====================================================
> +
> +The flows need to be configured and started by the traffic generator:
> +
> +|
> +
> ++------+---------+------------+---------------+------------+---------+
> +| Flow | Traffic | MAC | MAC | IPV4 | IPV4
> |
> +| | Gen. | Src. | Dst. | Src. | Dest.
> |
> +| | Port | Address | Address | Address | Address
> |
> ++------+---------+------------+---------------+------------+---------+
> +| 1 | TG0 | Random MAC | DUT Port0 Mac | Random IP |
> 2.1.1.1 |
> ++------+---------+------------+---------------+------------+---------+
> +| 2 | TG1 | Random Mac | DUT port1 Mac | Random IP |
> 1.1.1.1 |
> ++------+---------+------------+---------------+------------+---------+
> +
> +|
> +Frame sizes should be configured from 64,128,256,512,1024,2000, etc
> --
> 2.17.1
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-10-19 3:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-18 15:38 [dts] [PATCH V3 1/3] add test plan for performance thread test suite Wang Fei
2018-10-19 3:07 ` Tu, Lijuan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).