[dts][PATCH V1 0/9]test_plans: add perf test plans

[dts][PATCH V1 0/9]test_plans: add perf test plans

[Yingya Han]

add perf test plans

Yingya Han (9):
  add l3fwd_lpm_ipv4_rfc2544 test plan
  add l3fwd_lpm_ipv6 test plan
  add testpmd_perf test plan
  add vf_l3fwd_em_kernelpf test plan
  add vf_l3fwd_kernelpf test plan
  add vf_l3fwd_lpm_ipv4_kernelpf test plan
  add vf_l3fwd_lpm_ipv4_rfc2544_kernelpf test plan
  add vf_l3fwd_lpm_ipv6_kernelpf test plan
  add the index of test plan

 test_plans/index.rst                          |  10 +-
 .../l3fwd_lpm_ipv4_rfc2544_test_plan.rst      | 151 +++++++++++
 test_plans/l3fwd_lpm_ipv6_test_plan.rst       | 148 +++++++++++
 test_plans/testpmd_perf_test_plan.rst         | 171 +++++++++++++
 test_plans/vf_l3fwd_em_kernelpf_test_plan.rst | 201 +++++++++++++++
 test_plans/vf_l3fwd_kernelpf_test_plan.rst    | 241 ++++++++++++++++++
 .../vf_l3fwd_lpm_ipv4_kernelpf_test_plan.rst  | 160 ++++++++++++
 ...wd_lpm_ipv4_rfc2544_kernelpf_test_plan.rst | 162 ++++++++++++
 .../vf_l3fwd_lpm_ipv6_kernelpf_test_plan.rst  | 159 ++++++++++++
 9 files changed, 1402 insertions(+), 1 deletion(-)
 create mode 100644 test_plans/l3fwd_lpm_ipv4_rfc2544_test_plan.rst
 create mode 100644 test_plans/l3fwd_lpm_ipv6_test_plan.rst
 create mode 100644 test_plans/testpmd_perf_test_plan.rst
 create mode 100644 test_plans/vf_l3fwd_em_kernelpf_test_plan.rst
 create mode 100644 test_plans/vf_l3fwd_kernelpf_test_plan.rst
 create mode 100644 test_plans/vf_l3fwd_lpm_ipv4_kernelpf_test_plan.rst
 create mode 100644 test_plans/vf_l3fwd_lpm_ipv4_rfc2544_kernelpf_test_plan.rst
 create mode 100644 test_plans/vf_l3fwd_lpm_ipv6_kernelpf_test_plan.rst

-- 
2.34.1

[dts][PATCH V1 1/9]test_plans: add l3fwd_lpm_ipv4_rfc2544 test plan

[Yingya Han]

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 .../l3fwd_lpm_ipv4_rfc2544_test_plan.rst      | 151 ++++++++++++++++++
 1 file changed, 151 insertions(+)
 create mode 100644 test_plans/l3fwd_lpm_ipv4_rfc2544_test_plan.rst

diff --git a/test_plans/l3fwd_lpm_ipv4_rfc2544_test_plan.rst b/test_plans/l3fwd_lpm_ipv4_rfc2544_test_plan.rst
new file mode 100644
index 00000000..29b16b3e
--- /dev/null
+++ b/test_plans/l3fwd_lpm_ipv4_rfc2544_test_plan.rst
@@ -0,0 +1,151 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+   Copyright(c) 2022 Intel Corporation
+
+========================================================
+L3 forwarding rfc2544 test in LPM mode with IPV4 packets
+========================================================
+
+RFC2544 Zero packet loss test case: Used to determine the DUT throughput as defined in
+RFC1242(https://www.ietf.org/rfc/rfc1242.txt). Note RFC6201
+https://www.ietf.org/rfc/rfc6201.txt has updated RFC2544 and RFC1242. Please check the link
+for more details. In this case, RFC2544 test uses DPDK l3fwd as test application.
+
+Prerequisites
+=============
+
+Topology
+--------
+It requires at least 1 port connected traffic generator::
+        Port0 --- TG0
+
+2 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+
+4 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+        Port2 --- TG2
+        Port3 --- TG3
+
+Hardware
+--------
+This suite focus on l3fwd application, so any standard Ethernet Network Adapter is qualified.
+
+Software
+--------
+dpdk: git clone http://dpdk.org/git/dpdk
+trex: git clone http://trex-tgn.cisco.com/trex/release/v2.93.tar.gz
+
+
+Test Case
+=========
+Send a specific number of frames at a specific rate through the DUT and then
+count the frames that are transmitted by the DUT. If the count of offered frames is not equal
+to the count of received frames, the rate of the offered stream is reduced and the test is rerun.
+The throughput is the fastest rate at which the count of test frames transmitted by the DUT is
+equal to the number of test frames sent to it by the test equipment.
+
+The l3fwd application has a number of command line options, here list the key options will be tested::
+
+    ./dpdk-l3fwd [EAL options] -- -p PORTMASK
+                             [--force-max-simd-bitwidth=max-simd-bitwidth]
+                             --config(port,queue,lcore)[,(port,queue,lcore)]
+                             [--rx-queue-size NPKTS]
+                             [--tx-queue-size NPKTS]
+                             [--parse-ptype]
+                             [-L]|[-E]
+                             ...
+    Note:
+        --force-max-simd-bitwidth: This setting is used to determine the vector path for component selection.
+                                   And the default is avx2.
+        --rx-queue-size: Rx queue size in decimal and default is 1024.
+        --tx-queue-size: Tx queue size in decimal and default is 1024.
+        --parse-ptype: Optional, set to use software to analyze packet type.
+                       Without this option, hardware will check the packet type.
+        [-L]|[-E]: L3fwd uses the parameters "-L" and "-E" to correspond to LPM and EM modes respectively.
+                   And the default is LPM mode.
+
+Common Steps
+------------
+1. Bind tested ports to vfio-pci::
+
+    <dpdk_dir>#./usertools/dpdk-devbind.py -s
+    0000:17:00.0 'Device 1592' if=ens5f0 drv=ice unused=vfio-pci
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci <pci device id>
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci 0000:17:00.0
+
+2. Configure traffic generator to send traffic
+
+    Routing table for IPv4 packets
+      - In LPM mode, the LPM table used for packet routing is:
+
+    +-------+-----------------------+
+    |   #   | LPM prefix (IP/length)|
+    +=======+=======================+
+    |   0   |      198.18.0.0/24    |
+    +-------+-----------------------+
+    |   1   |      198.18.1.0/24    |
+    +-------+-----------------------+
+    |   2   |      198.18.2.0/24    |
+    +-------+-----------------------+
+    |   3   |      198.18.3.0/24    |
+    +-------+-----------------------+
+
+    The flows need to be configured and started by the traffic generator:
+      - IPv4 packets
+
+    +------+---------+------------+---------+
+    | Flow | Traffic | IPv4       | IPv4    |
+    |      | Gen.    | Dst.       | Src.    |
+    |      | Port    | Address    | Address |
+    +======+=========+============+=========+
+    |   1  |   TG0   | 198.18.1.1 |  Any Ip |
+    +------+---------+------------+---------+
+    |   2  |   TG1   | 198.18.0.1 |  Any Ip |
+    +------+---------+------------+---------+
+    |   3  |   TG2   | 198.18.3.1 |  Any Ip |
+    +------+---------+------------+---------+
+    |   4  |   TG3   | 198.18.2.1 |  Any Ip |
+    +------+---------+------------+---------+
+
+    Set the packet length : 64 bytes-1518 bytes
+    The IPV4 Src Address increase with the num 1024.
+
+3. Test result table
+
+    +-----------+------------+-------------+---------+
+    |  Fwd_core | Frame Size |  Throughput |   Rate  |
+    +===========+============+=============+=========+
+    |  1C/1T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  1C/1T    |   ...      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+
+
+Test Case: test_perf_rfc2544_ipv4_lpm
+-------------------------------------
+
+1. Bind PF ports to dpdk driver as common step 1.
+
+2. Launch l3fwd::
+
+     <build_dir>/examples/dpdk-l3fwd -l 5-8 -n 8 --force-max-simd-bitwidth=512 \
+     -- -p 0x1 --config "(0,0,5),(0,1,6),(0,2,7),(0,3,8)" --rx-queue-size 1024 \
+     --tx-queue-size 1024
+
+3. Configure traffic generator to send traffic as common step 2.
+
+4. Record Test results as common step 3.
-- 
2.34.1

[dts][PATCH V1 2/9]test_plans: add l3fwd_lpm_ipv6 test plan

[Yingya Han]

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 test_plans/l3fwd_lpm_ipv6_test_plan.rst | 148 ++++++++++++++++++++++++
 1 file changed, 148 insertions(+)
 create mode 100644 test_plans/l3fwd_lpm_ipv6_test_plan.rst

diff --git a/test_plans/l3fwd_lpm_ipv6_test_plan.rst b/test_plans/l3fwd_lpm_ipv6_test_plan.rst
new file mode 100644
index 00000000..287b8718
--- /dev/null
+++ b/test_plans/l3fwd_lpm_ipv6_test_plan.rst
@@ -0,0 +1,148 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+   Copyright(c) 2022 Intel Corporation
+
+================================================
+L3 forwarding test in LPM mode with IPV6 packets
+================================================
+
+This document provides the plan for testing the performance of Intel Ethernet Controller.
+The Layer-3 Forwarding  performance results are produced using ``l3fwd`` application.
+For detail test plan, please refer to ``l3fwd_test_plan.rst``.
+
+Prerequisites
+=============
+
+Topology
+--------
+It requires at least 1 port connected traffic generator::
+        Port0 --- TG0
+
+2 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+
+4 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+        Port2 --- TG2
+        Port3 --- TG3
+
+Hardware
+--------
+This suite focus on l3fwd application, so any standard Ethernet Network Adapter is qualified.
+
+Software
+--------
+dpdk: git clone http://dpdk.org/git/dpdk
+trex: git clone http://trex-tgn.cisco.com/trex/release/v2.93.tar.gz
+
+
+Test Case
+=========
+The test case check the throughput result with lpm mode and ipv6, in the case,
+we will send the bi-direction flows with line rate, then we can check the
+passthrough rate.
+
+The l3fwd application has a number of command line options, here list the key options will be tested::
+
+    ./dpdk-l3fwd [EAL options] -- -p PORTMASK
+                             [--force-max-simd-bitwidth=max-simd-bitwidth]
+                             --config(port,queue,lcore)[,(port,queue,lcore)]
+                             [--rx-queue-size NPKTS]
+                             [--tx-queue-size NPKTS]
+                             [--parse-ptype]
+                             [-L]|[-E]
+                             ...
+    Note:
+        --force-max-simd-bitwidth: This setting is used to determine the vector path for component selection.
+                                   And the default is avx2.
+        --rx-queue-size: Rx queue size in decimal and default is 1024.
+        --tx-queue-size: Tx queue size in decimal and default is 1024.
+        --parse-ptype: Optional, set to use software to analyze packet type.
+                       Without this option, hardware will check the packet type.
+        [-L]|[-E]: L3fwd uses the parameters "-L" and "-E" to correspond to LPM and EM modes respectively.
+                   And the default is LPM mode.
+
+Common Steps
+------------
+1. Bind tested ports to vfio-pci::
+
+    <dpdk_dir>#./usertools/dpdk-devbind.py -s
+    0000:17:00.0 'Device 1592' if=ens5f0 drv=ice unused=vfio-pci
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci <pci device id>
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci 0000:17:00.0
+
+2. Configure traffic generator to send traffic
+
+    Routing table for IPv6 packets
+      - In LPM mode, the LPM table used for packet routing is:
+
+    +-------+--------------------------------------------+
+    |   #   |           LPM prefix (IP/length)           |
+    +=======+============================================+
+    |   0   | 2001:0200:0000:0000:0000:0000:0000:0000/64 |
+    +-------+--------------------------------------------+
+    |   1   | 2001:0200:0000:0001:0000:0000:0000:0000/64 |
+    +-------+--------------------------------------------+
+    |   2   | 2001:0200:0000:0002:0000:0000:0000:0000/64 |
+    +-------+--------------------------------------------+
+    |   3   | 2001:0200:0000:0003:0000:0000:0000:0000/64 |
+    +-------+--------------------------------------------+
+
+    The flows need to be configured and started by the traffic generator:
+      - IPv6 packets
+
+    +------+---------+-----------------------------------------+---------+
+    | Flow | Traffic |                                         | IPv6    |
+    |      | Gen.    |           IPV6 Dst. Address             | Src.    |
+    |      | Port    |                                         | Address |
+    +======+=========+=========================================+=========+
+    |   1  |   TG0   | 2001:0200:0000:0000:0000:0000:0000:0000 |  Any Ip |
+    +------+---------+-----------------------------------------+---------+
+    |   2  |   TG1   | 2001:0200:0000:0001:0000:0000:0000:0000 |  Any Ip |
+    +------+---------+-----------------------------------------+---------+
+    |   3  |   TG2   | 2001:0200:0000:0002:0000:0000:0000:0000 |  Any Ip |
+    +------+---------+-----------------------------------------+---------+
+    |   4  |   TG3   | 2001:0200:0000:0003:0000:0000:0000:0000 |  Any Ip |
+    +------+---------+-----------------------------------------+---------+
+
+    Set the packet length : 66 bytes-1518 bytes
+    The IPV6 Src Address increase with the num 1024.
+
+3. Test result table
+
+    +-----------+------------+-------------+---------+
+    |  Fwd_core | Frame Size |  Throughput |   Rate  |
+    +===========+============+=============+=========+
+    |  1C/1T    |    66      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  1C/1T    |   ...      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    66      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    66      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    66      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+
+
+Test Case: test_perf_throughput_ipv6_lpm
+----------------------------------------
+
+1. Bind PF ports to dpdk driver as common step 1.
+
+2. Launch l3fwd::
+
+     <build_dir>/examples/dpdk-l3fwd -l 5-8 -n 8 --force-max-simd-bitwidth=512 \
+     -- -p 0x1 --config "(0,0,5),(0,1,6),(0,2,7),(0,3,8)" --rx-queue-size 1024 \
+     --tx-queue-size 1024
+
+3. Configure traffic generator to send traffic as common step 2.
+
+4. Record Test results as common step 3.
-- 
2.34.1

[dts][PATCH V1 3/9]test_plans: add testpmd_perf test plan

[Yingya Han]

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 test_plans/testpmd_perf_test_plan.rst | 171 ++++++++++++++++++++++++++
 1 file changed, 171 insertions(+)
 create mode 100644 test_plans/testpmd_perf_test_plan.rst

diff --git a/test_plans/testpmd_perf_test_plan.rst b/test_plans/testpmd_perf_test_plan.rst
new file mode 100644
index 00000000..b0e1a730
--- /dev/null
+++ b/test_plans/testpmd_perf_test_plan.rst
@@ -0,0 +1,171 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+   Copyright(c) 2022 Intel Corporation
+
+===========================================
+TestPmd rfc2544 test with IPV4/IPV6 packets
+===========================================
+
+This document provides rfc2544 tests for the userland Ethernet Controller Poll Mode Driver (PMD).
+The userland PMD application runs the ``IO forwarding mode`` test which described in the PMD test
+plan document with different parameters for the configuration of NIC ports.
+
+RFC2544 Zero packet loss test case: Used to determine the DUT throughput as defined in
+RFC1242(https://www.ietf.org/rfc/rfc1242.txt). Note RFC6201
+https://www.ietf.org/rfc/rfc6201.txt has updated RFC2544 and RFC1242. Please check the link
+for more details. In this case, RFC2544 test uses dpdk-testpmd as test application.
+
+Prerequisites
+=============
+
+Topology
+--------
+It requires at least 1 port connected traffic generator::
+        Port0 --- TG0
+
+2 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+
+4 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+        Port2 --- TG2
+        Port3 --- TG3
+
+Hardware
+--------
+This suite focus on dpdk-testpmd application, so any standard Ethernet Network Adapter is qualified.
+
+Software
+--------
+dpdk: git clone http://dpdk.org/git/dpdk
+trex: git clone http://trex-tgn.cisco.com/trex/release/v2.93.tar.gz
+
+
+Test Case
+=========
+Send a specific number of frames at a specific rate through the DUT and then
+count the frames that are transmitted by the DUT. If the count of offered frames is not equal
+to the count of received frames, the rate of the offered stream is reduced and the test is rerun.
+The throughput is the fastest rate at which the count of test frames transmitted by the DUT is
+equal to the number of test frames sent to it by the test equipment.
+
+Common Steps
+------------
+1. Bind tested ports to vfio-pci::
+
+    <dpdk_dir>#./usertools/dpdk-devbind.py -s
+    0000:17:00.0 'Device 1592' if=ens5f0 drv=ice unused=vfio-pci
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci <pci device id>
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci 0000:17:01.0
+
+2. Configure traffic generator to send traffic
+
+    Routing table for IPv4 packets:
+
+        +-------+-----------------------+
+        |   #   |    IPv4 (IP/length)   |
+        +=======+=======================+
+        |   0   |      198.18.0.0/24    |
+        +-------+-----------------------+
+        |   1   |      198.18.1.0/24    |
+        +-------+-----------------------+
+        |   2   |      198.18.2.0/24    |
+        +-------+-----------------------+
+        |   3   |      198.18.3.0/24    |
+        +-------+-----------------------+
+
+    Routing table for IPv6 packets:
+
+        +-------+--------------------------------------------+
+        |   #   |              IPv6 (IP/length)              |
+        +=======+============================================+
+        |   0   | 2001:0200:0000:0000:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+        |   1   | 2001:0200:0000:0001:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+        |   2   | 2001:0200:0000:0002:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+        |   3   | 2001:0200:0000:0003:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+
+    The flows need to be configured and started by the traffic generator:
+        - IPv4 packets
+
+        +------+---------+------------+---------+
+        | Flow | Traffic | IPv4       | IPv4    |
+        |      | Gen.    | Dst.       | Src.    |
+        |      | Port    | Address    | Address |
+        +======+=========+============+=========+
+        |   1  |   TG0   | 198.18.1.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   2  |   TG1   | 198.18.0.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   3  |   TG2   | 198.18.3.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   4  |   TG3   | 198.18.2.1 |  Any Ip |
+        +------+---------+------------+---------+
+
+        Set the packet length : 64 bytes-1518 bytes
+        The IPV4 Src Address increase with the num 1024.
+
+        - IPv6 packets
+
+        +------+---------+-----------------------------------------+---------+
+        | Flow | Traffic |                                         | IPv6    |
+        |      | Gen.    |           IPV6 Dst. Address             | Src.    |
+        |      | Port    |                                         | Address |
+        +======+=========+=========================================+=========+
+        |   1  |   TG0   | 2001:0200:0000:0000:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   2  |   TG1   | 2001:0200:0000:0001:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   3  |   TG2   | 2001:0200:0000:0002:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   4  |   TG3   | 2001:0200:0000:0003:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+
+        Set the packet length : 66 bytes-1518 bytes
+        The IPV6 Src Address increase with the num 1024.
+
+3. Test result table
+
+    +-----------+------------+-------------+---------+
+    |  Fwd_core | Frame Size |  Throughput |   Rate  |
+    +===========+============+=============+=========+
+    |  1C/1T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  1C/1T    |   ...      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+
+
+Test Case: testpmd rfc2544 performance with IPv4/IPv6 Packets
+-------------------------------------------------------------
+
+1. Bind tested ports to dpdk driver as common step 1.
+
+2. Start dpdk-testpmd::
+
+    <build_dir>/app/dpdk-testpmd -l 5,6 -n 8 --force-max-simd-bitwidth=512 \
+     -- -i --portmask=0x1 --rxq=1 --txq=1 --txd=1024 --rxd=1024 --forward=io \
+     --nb-cores=1
+
+    Note:
+      -force-max-simd-bitwidth: This setting is used to determine the vector path for component selection.
+                                And the default is avx2.
+
+3. Configure traffic generator to send traffic as common step 2.
+
+4. Record Test results as common step 3.
-- 
2.34.1

[dts][PATCH V1 4/9]test_plans: add vf_l3fwd_em_kernelpf test plan

[Yingya Han]

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 test_plans/vf_l3fwd_em_kernelpf_test_plan.rst | 201 ++++++++++++++++++
 1 file changed, 201 insertions(+)
 create mode 100644 test_plans/vf_l3fwd_em_kernelpf_test_plan.rst

diff --git a/test_plans/vf_l3fwd_em_kernelpf_test_plan.rst b/test_plans/vf_l3fwd_em_kernelpf_test_plan.rst
new file mode 100644
index 00000000..2613e8a8
--- /dev/null
+++ b/test_plans/vf_l3fwd_em_kernelpf_test_plan.rst
@@ -0,0 +1,201 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+   Copyright(c) 2022 Intel Corporation
+
+==========================================
+VF L3 forwarding kernel PF test in EM mode
+==========================================
+
+This document provides benchmark test for NIC VFs which are created from
+kernel PFs or. These tests use l3fwd as a simple forwarder between NIC vfs.
+The goal of this test plan is to have a tested benchmark between NIC vfs.
+The Layer-3 Forwarding  performance results are produced using ``l3fwd`` application.
+For detail test plan, please refer to ``l3fwd_test_plan.rst``.
+
+Prerequisites
+=============
+
+Topology
+--------
+It requires at least 1 port connected traffic generator::
+        Port0 --- TG0
+
+2 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+
+4 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+        Port2 --- TG2
+        Port3 --- TG3
+
+Hardware
+--------
+This suite focus on l3fwd application, so any standard Ethernet Network Adapter is qualified.
+
+Software
+--------
+dpdk: git clone http://dpdk.org/git/dpdk
+trex: git clone http://trex-tgn.cisco.com/trex/release/v2.93.tar.gz
+
+
+Test Case
+=========
+The test case check the throughput result with em mode and ipv4/ipv6, in the case,
+we will send the bi-direction flows with line rate, then we can check the passthrough rate.
+
+The l3fwd application has a number of command line options, here list the key options will be tested::
+
+    ./dpdk-l3fwd [EAL options] -- -p PORTMASK
+                             [--force-max-simd-bitwidth=max-simd-bitwidth]
+                             --config(port,queue,lcore)[,(port,queue,lcore)]
+                             [--rx-queue-size NPKTS]
+                             [--tx-queue-size NPKTS]
+                             [--parse-ptype]
+                             [-L]|[-E]
+                             ...
+    Note:
+        --force-max-simd-bitwidth: This setting is used to determine the vector path for component selection.
+                                   And the default is avx2.
+        --rx-queue-size: Rx queue size in decimal and default is 1024.
+        --tx-queue-size: Tx queue size in decimal and default is 1024.
+        --parse-ptype: Optional, set to use software to analyze packet type.
+                       Without this option, hardware will check the packet type.
+        [-L]|[-E]: L3fwd uses the parameters "-L" and "-E" to correspond to LPM and EM modes respectively.
+                   And the default is LPM mode.
+
+Common Steps
+------------
+1. Bind PF ports to kernel driver, i40e or ice, then create 1 VF from each PF,
+   take E810 for example::
+
+    <dpdk_dir>#echo 1 > /sys/bus/pci/devices/0000\:17\:00.0/sriov_numvfs
+
+   Set vf mac address::
+
+    <dpdk_dir>#ip link set ens5f0 vf 0 mac 00:12:34:56:78:01
+
+   Bind all the created VFs to vfio-pci::
+
+    <dpdk_dir>#./usertools/dpdk-devbind.py -s
+    0000:17:00.0 'Device 1592' if=ens5f0 drv=ice unused=vfio-pci
+    0000:17:01.0 'Device 1592' if=ens5f0v0 drv=iavf unused=vfio-pci
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci <pci device id>
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci 0000:17:01.0
+
+2. Configure traffic generator to send traffic
+
+    Routing table for IPv4 packets
+        - In EM mode, the EM table used for packet routing is:
+
+        +-------+-------------+---------+-------------+-----------+-----------+
+        | Entry | IPv4        | IPv4    | Port        | Port      | L4        |
+        |   #   | destination | source  | destination | source    | protocol  |
+        |       | address     | address |             |           |           |
+        +=======+=============+=========+=============+===========+===========+
+        |   0   | 198.18.0.0  | Random  |     10      |     1     |    UDP    |
+        +-------+-------------+---------+-------------+-----------+-----------+
+        |   1   | 198.18.1.0  | Random  |     10      |     1     |    UDP    |
+        +-------+-------------+---------+-------------+-----------+-----------+
+        |   2   | 198.18.2.0  | Random  |     11      |     1     |    UDP    |
+        +-------+-------------+---------+-------------+-----------+-----------+
+        |   3   | 198.18.3.0  | Random  |     11      |     1     |    UDP    |
+        +-------+-------------+---------+-------------+-----------+-----------+
+
+    Routing table for IPv6 packets
+        - In EM mode, the EM table used for packet routing is:
+
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+        | Entry | IPv6 destination address  | IPv6 source address       | Port        | Port   | L4       |
+        |       |                           |                           | destination | source | protocol |
+        +=======+===========================+===========================+=============+========+==========+
+        |   0   | 2001:0200:0000:0000:0000:\|                           |             |        |          |
+        |       |       0000:0000:0000      |          Random           |     10      |    1   |   UDP    |
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+        |   1   | 2001:0200:0000:0001:0000:\|                           |             |        |          |
+        |       |       0000:0000:0000      |          Random           |     10      |    1   |   UDP    |
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+        |   2   | 2001:0200:0000:0002:0000:\|                           |             |        |          |
+        |       |       0000:0000:0000      |          Random           |     11      |    1   |   UDP    |
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+        |   3   | 2001:0200:0000:0003:0000:\|                           |             |        |          |
+        |       |       0000:0000:0000      |          Random           |     11      |    1   |   UDP    |
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+
+
+    The flows need to be configured and started by the traffic generator:
+        - IPv4 packets
+
+        +------+---------+------------+---------+
+        | Flow | Traffic | IPv4       | IPv4    |
+        |      | Gen.    | Dst.       | Src.    |
+        |      | Port    | Address    | Address |
+        +======+=========+============+=========+
+        |   1  |   TG0   | 198.18.1.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   2  |   TG1   | 198.18.0.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   3  |   TG2   | 198.18.3.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   4  |   TG3   | 198.18.2.1 |  Any Ip |
+        +------+---------+------------+---------+
+
+        Set the packet length : 64 bytes-1518 bytes
+        The IPV4 Src Address increase with the num 1024.
+
+        - IPv6 packets
+
+        +------+---------+-----------------------------------------+---------+
+        | Flow | Traffic |                                         | IPv6    |
+        |      | Gen.    |           IPV6 Dst. Address             | Src.    |
+        |      | Port    |                                         | Address |
+        +======+=========+=========================================+=========+
+        |   1  |   TG0   | 2001:0200:0000:0000:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   2  |   TG1   | 2001:0200:0000:0001:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   3  |   TG2   | 2001:0200:0000:0002:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   4  |   TG3   | 2001:0200:0000:0003:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+
+        Set the packet length : 66 bytes-1518 bytes
+        The IPV6 Src Address increase with the num 1024.
+
+3. Test result table
+
+    +-----------+------------+-------------+---------+
+    |  Fwd_core | Frame Size |  Throughput |   Rate  |
+    +===========+============+=============+=========+
+    |  1C/1T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  1C/1T    |   ...      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+
+
+Test Case:  VF L3 Forwarding in EM Mode with IPv4/IPv6 Packets
+--------------------------------------------------------------
+
+1. Bind VF ports to dpdk driver as common step 1.
+
+2. Launch l3fwd::
+
+     <build_dir>/examples/dpdk-l3fwd -l 5-8 -n 8 --force-max-simd-bitwidth=512 \
+     -- -p 0x1 --config "(0,0,5),(0,1,6),(0,2,7),(0,3,8)" --rx-queue-size 1024 \
+     --tx-queue-size 1024 -E --parse-ptype
+
+3. Configure traffic generator to send traffic as common step 2.
+
+4. Record Test results as common step 3.
-- 
2.34.1

[dts][PATCH V1 5/9]test_plans: add vf_l3fwd_kernelpf test plan

[Yingya Han]

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 test_plans/vf_l3fwd_kernelpf_test_plan.rst | 241 +++++++++++++++++++++
 1 file changed, 241 insertions(+)
 create mode 100644 test_plans/vf_l3fwd_kernelpf_test_plan.rst

diff --git a/test_plans/vf_l3fwd_kernelpf_test_plan.rst b/test_plans/vf_l3fwd_kernelpf_test_plan.rst
new file mode 100644
index 00000000..645cadfb
--- /dev/null
+++ b/test_plans/vf_l3fwd_kernelpf_test_plan.rst
@@ -0,0 +1,241 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+   Copyright(c) 2022 Intel Corporation
+
+================================
+VF L3 forwarding kernel PF tests
+================================
+
+This document provides benchmark test for NIC VFs which are created from
+kernel PFs or. These tests use l3fwd as a simple forwarder between NIC vfs.
+The goal of this test plan is to have a tested benchmark between NIC vfs.
+The Layer-3 Forwarding  performance results are produced using ``l3fwd`` application.
+For detail test plan, please refer to ``l3fwd_test_plan.rst``.
+
+Prerequisites
+=============
+
+Topology
+--------
+It requires at least 1 port connected traffic generator::
+        Port0 --- TG0
+
+2 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+
+4 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+        Port2 --- TG2
+        Port3 --- TG3
+
+Hardware
+--------
+This suite focus on l3fwd application, so any standard Ethernet Network Adapter is qualified.
+
+Software
+--------
+dpdk: git clone http://dpdk.org/git/dpdk
+trex: git clone http://trex-tgn.cisco.com/trex/release/v2.93.tar.gz
+
+
+Test Case
+=========
+
+The suite includes the throughput tests and rfc544 tests.
+1. Throughput:
+
+    - The test case check the throughput result with lpm/em mode and ipv4/ipv6, in the case,
+      we will send the bi-direction flows with line rate, then we can check the passthrough rate.
+
+2. RFC2544 Zero packet loss test:
+
+    - Send a specific number of frames at a specific rate through the DUT and then
+      count the frames that are transmitted by the DUT. If the count of offered frames is not equal
+      to the count of received frames, the rate of the offered stream is reduced and the test is rerun.
+      The throughput is the fastest rate at which the count of test frames transmitted by the DUT is
+      equal to the number of test frames sent to it by the test equipment.
+
+The l3fwd application has a number of command line options, here list the key options will be tested::
+
+    ./dpdk-l3fwd [EAL options] -- -p PORTMASK
+                             [--force-max-simd-bitwidth=max-simd-bitwidth]
+                             --config(port,queue,lcore)[,(port,queue,lcore)]
+                             [--rx-queue-size NPKTS]
+                             [--tx-queue-size NPKTS]
+                             [--parse-ptype]
+                             [-L]|[-E]
+                             ...
+    Note:
+        --force-max-simd-bitwidth: This setting is used to determine the vector path for component selection.
+                                   And the default is avx2.
+        --rx-queue-size: Rx queue size in decimal and default is 1024.
+        --tx-queue-size: Tx queue size in decimal and default is 1024.
+        --parse-ptype: Optional, set to use software to analyze packet type.
+                       Without this option, hardware will check the packet type.
+        [-L]|[-E]: L3fwd uses the parameters "-L" and "-E" to correspond to LPM and EM modes respectively.
+                   And the default is LPM mode.
+
+Common Steps
+------------
+1. Bind PF ports to kernel driver, i40e or ice, then create 1 VF from each PF,
+   take E810 for example::
+
+    <dpdk_dir>#echo 1 > /sys/bus/pci/devices/0000\:17\:00.0/sriov_numvfs
+
+   Set vf mac address::
+
+    <dpdk_dir>#ip link set ens5f0 vf 0 mac 00:12:34:56:78:01
+
+   Bind all the created VFs to vfio-pci::
+
+    <dpdk_dir>#./usertools/dpdk-devbind.py -s
+    0000:17:00.0 'Device 1592' if=ens5f0 drv=ice unused=vfio-pci
+    0000:17:01.0 'Device 1592' if=ens5f0v0 drv=iavf unused=vfio-pci
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci <pci device id>
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci 0000:17:01.0
+
+2. Configure traffic generator to send traffic
+
+    Routing table for IPv4 packets
+        - In LPM mode, the LPM table used for packet routing is:
+
+        +-------+-----------------------+
+        |   #   | LPM prefix (IP/length)|
+        +=======+=======================+
+        |   0   |      198.18.0.0/24    |
+        +-------+-----------------------+
+        |   1   |      198.18.1.0/24    |
+        +-------+-----------------------+
+        |   2   |      198.18.2.0/24    |
+        +-------+-----------------------+
+        |   3   |      198.18.3.0/24    |
+        +-------+-----------------------+
+
+        - In EM mode, the EM table used for packet routing is:
+
+        +-------+-------------+---------+-------------+-----------+-----------+
+        | Entry | IPv4        | IPv4    | Port        | Port      | L4        |
+        |   #   | destination | source  | destination | source    | protocol  |
+        |       | address     | address |             |           |           |
+        +=======+=============+=========+=============+===========+===========+
+        |   0   | 198.18.0.0  | Random  |     10      |     1     |    UDP    |
+        +-------+-------------+---------+-------------+-----------+-----------+
+        |   1   | 198.18.1.0  | Random  |     10      |     1     |    UDP    |
+        +-------+-------------+---------+-------------+-----------+-----------+
+        |   2   | 198.18.2.0  | Random  |     11      |     1     |    UDP    |
+        +-------+-------------+---------+-------------+-----------+-----------+
+        |   3   | 198.18.3.0  | Random  |     11      |     1     |    UDP    |
+        +-------+-------------+---------+-------------+-----------+-----------+
+
+    Routing table for IPv6 packets
+        - In LPM mode, the LPM table used for packet routing is:
+
+        +-------+--------------------------------------------+
+        |   #   |           LPM prefix (IP/length)           |
+        +=======+============================================+
+        |   0   | 2001:0200:0000:0000:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+        |   1   | 2001:0200:0000:0001:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+        |   2   | 2001:0200:0000:0002:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+        |   3   | 2001:0200:0000:0003:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+
+        - In EM mode, the EM table used for packet routing is:
+
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+        | Entry | IPv6 destination address  | IPv6 source address       | Port        | Port   | L4       |
+        |       |                           |                           | destination | source | protocol |
+        +=======+===========================+===========================+=============+========+==========+
+        |   0   | 2001:0200:0000:0000:0000:\|                           |             |        |          |
+        |       |       0000:0000:0000      |          Random           |     10      |    1   |   UDP    |
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+        |   1   | 2001:0200:0000:0001:0000:\|                           |             |        |          |
+        |       |       0000:0000:0000      |          Random           |     10      |    1   |   UDP    |
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+        |   2   | 2001:0200:0000:0002:0000:\|                           |             |        |          |
+        |       |       0000:0000:0000      |          Random           |     11      |    1   |   UDP    |
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+        |   3   | 2001:0200:0000:0003:0000:\|                           |             |        |          |
+        |       |       0000:0000:0000      |          Random           |     11      |    1   |   UDP    |
+        +-------+---------------------------+---------------------------+-------------+--------+----------+
+
+
+    The flows need to be configured and started by the traffic generator:
+        - IPv4 packets
+
+        +------+---------+------------+---------+
+        | Flow | Traffic | IPv4       | IPv4    |
+        |      | Gen.    | Dst.       | Src.    |
+        |      | Port    | Address    | Address |
+        +======+=========+============+=========+
+        |   1  |   TG0   | 198.18.1.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   2  |   TG1   | 198.18.0.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   3  |   TG2   | 198.18.3.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   4  |   TG3   | 198.18.2.1 |  Any Ip |
+        +------+---------+------------+---------+
+
+        Set the packet length : 64 bytes-1518 bytes
+        The IPV4 Src Address increase with the num 1024.
+
+        - IPv6 packets
+
+        +------+---------+-----------------------------------------+---------+
+        | Flow | Traffic |                                         | IPv6    |
+        |      | Gen.    |           IPV6 Dst. Address             | Src.    |
+        |      | Port    |                                         | Address |
+        +======+=========+=========================================+=========+
+        |   1  |   TG0   | 2001:0200:0000:0000:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   2  |   TG1   | 2001:0200:0000:0001:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   3  |   TG2   | 2001:0200:0000:0002:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   4  |   TG3   | 2001:0200:0000:0003:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+
+        Set the packet length : 66 bytes-1518 bytes
+        The IPV6 Src Address increase with the num 1024.
+
+3. Test result table
+
+    +-----------+------------+-------------+---------+
+    |  Fwd_core | Frame Size |  Throughput |   Rate  |
+    +===========+============+=============+=========+
+    |  1C/1T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  1C/1T    |   ...      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+
+
+Test Case: VF L3 Forwarding (in EM/LPM Mode) with IPv4/IPv6 Packets
+-------------------------------------------------------------------
+
+1. Bind VF ports to dpdk driver as common step 1.
+
+2. Launch l3fwd::
+
+     <build_dir>/examples/dpdk-l3fwd -l 5-8 -n 8 --force-max-simd-bitwidth=512 \
+     -- -p 0x1 --config "(0,0,5),(0,1,6),(0,2,7),(0,3,8)" --rx-queue-size 1024 \
+     --tx-queue-size 1024 --parse-ptype
+
+3. Configure traffic generator to send traffic as common step 2.
+
+4. Record Test results as common step 3.
-- 
2.34.1

[dts][PATCH V1 6/9]test_plans: add vf_l3fwd_lpm_ipv4_kernelpf test plan

[Yingya Han]

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 .../vf_l3fwd_lpm_ipv4_kernelpf_test_plan.rst  | 160 ++++++++++++++++++
 1 file changed, 160 insertions(+)
 create mode 100644 test_plans/vf_l3fwd_lpm_ipv4_kernelpf_test_plan.rst

diff --git a/test_plans/vf_l3fwd_lpm_ipv4_kernelpf_test_plan.rst b/test_plans/vf_l3fwd_lpm_ipv4_kernelpf_test_plan.rst
new file mode 100644
index 00000000..3a4200c9
--- /dev/null
+++ b/test_plans/vf_l3fwd_lpm_ipv4_kernelpf_test_plan.rst
@@ -0,0 +1,160 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+   Copyright(c) 2022 Intel Corporation
+
+=============================================================
+VF L3 forwarding kernel PF test in LPM mode with IPV4 packets
+=============================================================
+
+This document provides benchmark test for NIC VFs which are created from
+kernel PFs or. These tests use l3fwd as a simple forwarder between NIC vfs.
+The goal of this test plan is to have a tested benchmark between NIC vfs.
+The Layer-3 Forwarding  performance results are produced using ``l3fwd`` application.
+For detail test plan, please refer to ``l3fwd_test_plan.rst``.
+
+Prerequisites
+=============
+
+Topology
+--------
+It requires at least 1 port connected traffic generator::
+        Port0 --- TG0
+
+2 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+
+4 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+        Port2 --- TG2
+        Port3 --- TG3
+
+Hardware
+--------
+This suite focus on l3fwd application, so any standard Ethernet Network Adapter is qualified.
+
+Software
+--------
+dpdk: git clone http://dpdk.org/git/dpdk
+trex: git clone http://trex-tgn.cisco.com/trex/release/v2.93.tar.gz
+
+
+Test Case
+=========
+The test case check the throughput result with lpm mode and ipv4, in the case,
+we will send the bi-direction flows with line rate, then we can check the
+passthrough rate.
+
+The l3fwd application has a number of command line options, here list the key options will be tested::
+
+    ./dpdk-l3fwd [EAL options] -- -p PORTMASK
+                             [--force-max-simd-bitwidth=max-simd-bitwidth]
+                             --config(port,queue,lcore)[,(port,queue,lcore)]
+                             [--rx-queue-size NPKTS]
+                             [--tx-queue-size NPKTS]
+                             [--parse-ptype]
+                             [-L]|[-E]
+                             ...
+    Note:
+        --force-max-simd-bitwidth: This setting is used to determine the vector path for component selection.
+                                   And the default is avx2.
+        --rx-queue-size: Rx queue size in decimal and default is 1024.
+        --tx-queue-size: Tx queue size in decimal and default is 1024.
+        --parse-ptype: Optional, set to use software to analyze packet type.
+                       Without this option, hardware will check the packet type.
+        [-L]|[-E]: L3fwd uses the parameters "-L" and "-E" to correspond to LPM and EM modes respectively.
+                   And the default is LPM mode.
+
+Common Steps
+------------
+1. Bind PF ports to kernel driver, i40e or ice, then create 1 VF from each PF,
+   take E810 for example::
+
+    <dpdk_dir>#echo 1 > /sys/bus/pci/devices/0000\:17\:00.0/sriov_numvfs
+
+   Set vf mac address::
+
+    <dpdk_dir>#ip link set ens5f0 vf 0 mac 00:12:34:56:78:01
+
+   Bind all the created VFs to vfio-pci::
+
+    <dpdk_dir>#./usertools/dpdk-devbind.py -s
+    0000:17:00.0 'Device 1592' if=ens5f0 drv=ice unused=vfio-pci
+    0000:17:01.0 'Device 1592' if=ens5f0v0 drv=iavf unused=vfio-pci
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci <pci device id>
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci 0000:17:01.0
+
+2. Configure traffic generator to send traffic
+
+    Routing table for IPv4 packets
+        - In LPM mode, the LPM table used for packet routing is:
+
+        +-------+-----------------------+
+        |   #   | LPM prefix (IP/length)|
+        +=======+=======================+
+        |   0   |      198.18.0.0/24    |
+        +-------+-----------------------+
+        |   1   |      198.18.1.0/24    |
+        +-------+-----------------------+
+        |   2   |      198.18.2.0/24    |
+        +-------+-----------------------+
+        |   3   |      198.18.3.0/24    |
+        +-------+-----------------------+
+
+    The flows need to be configured and started by the traffic generator:
+        - IPv4 packets
+
+        +------+---------+------------+---------+
+        | Flow | Traffic | IPv4       | IPv4    |
+        |      | Gen.    | Dst.       | Src.    |
+        |      | Port    | Address    | Address |
+        +======+=========+============+=========+
+        |   1  |   TG0   | 198.18.1.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   2  |   TG1   | 198.18.0.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   3  |   TG2   | 198.18.3.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   4  |   TG3   | 198.18.2.1 |  Any Ip |
+        +------+---------+------------+---------+
+
+        Set the packet length : 64 bytes-1518 bytes
+        The IPV4 Src Address increase with the num 1024.
+
+3. Test result table
+
+    +-----------+------------+-------------+---------+
+    |  Fwd_core | Frame Size |  Throughput |   Rate  |
+    +===========+============+=============+=========+
+    |  1C/1T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  1C/1T    |   ...      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+
+
+Test Case: test_perf_vf_throughput_ipv4_lpm
+-------------------------------------------
+
+1. Bind VF ports to dpdk driver as common step 1.
+
+2. Launch l3fwd::
+
+     <build_dir>/examples/dpdk-l3fwd -l 5-8 -n 8 --force-max-simd-bitwidth=512 \
+     -- -p 0x1 --config "(0,0,5),(0,1,6),(0,2,7),(0,3,8)" --rx-queue-size 1024 \
+     --tx-queue-size 1024 --parse-ptype
+
+3. Configure traffic generator to send traffic as common step 2.
+
+4. Record Test results as common step 3.
-- 
2.34.1

[dts][PATCH V1 7/9]test_plans: add vf_l3fwd_lpm_ipv4_rfc2544_kernelpf test plan

[Yingya Han]

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 ...wd_lpm_ipv4_rfc2544_kernelpf_test_plan.rst | 162 ++++++++++++++++++
 1 file changed, 162 insertions(+)
 create mode 100644 test_plans/vf_l3fwd_lpm_ipv4_rfc2544_kernelpf_test_plan.rst

diff --git a/test_plans/vf_l3fwd_lpm_ipv4_rfc2544_kernelpf_test_plan.rst b/test_plans/vf_l3fwd_lpm_ipv4_rfc2544_kernelpf_test_plan.rst
new file mode 100644
index 00000000..d6e7a936
--- /dev/null
+++ b/test_plans/vf_l3fwd_lpm_ipv4_rfc2544_kernelpf_test_plan.rst
@@ -0,0 +1,162 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+   Copyright(c) 2022 Intel Corporation
+
+=====================================================================
+VF L3 forwarding kernel PF rfc2544 test in LPM mode with IPV4 packets
+=====================================================================
+
+This document provides benchmark test for NIC VFs which are created from
+kernel PFs or. These tests use l3fwd as a simple forwarder between NIC vfs.
+The goal of this test plan is to have a tested benchmark between NIC vfs.
+The Layer-3 Forwarding  performance results are produced using ``l3fwd`` application.
+For detail test plan, please refer to ``l3fwd_test_plan.rst``.
+
+Prerequisites
+=============
+
+Topology
+--------
+It requires at least 1 port connected traffic generator::
+        Port0 --- TG0
+
+2 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+
+4 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+        Port2 --- TG2
+        Port3 --- TG3
+
+Hardware
+--------
+This suite focus on l3fwd application, so any standard Ethernet Network Adapter is qualified.
+
+Software
+--------
+dpdk: git clone http://dpdk.org/git/dpdk
+trex: git clone http://trex-tgn.cisco.com/trex/release/v2.93.tar.gz
+
+
+Test Case
+=========
+Send a specific number of frames at a specific rate through the DUT and then
+count the frames that are transmitted by the DUT. If the count of offered frames is not equal
+to the count of received frames, the rate of the offered stream is reduced and the test is rerun.
+The throughput is the fastest rate at which the count of test frames transmitted by the DUT is
+equal to the number of test frames sent to it by the test equipment.
+
+The l3fwd application has a number of command line options, here list the key options will be tested::
+
+    ./dpdk-l3fwd [EAL options] -- -p PORTMASK
+                             [--force-max-simd-bitwidth=max-simd-bitwidth]
+                             --config(port,queue,lcore)[,(port,queue,lcore)]
+                             [--rx-queue-size NPKTS]
+                             [--tx-queue-size NPKTS]
+                             [--parse-ptype]
+                             [-L]|[-E]
+                             ...
+    Note:
+        --force-max-simd-bitwidth: This setting is used to determine the vector path for component selection.
+                                   And the default is avx2.
+        --rx-queue-size: Rx queue size in decimal and default is 1024.
+        --tx-queue-size: Tx queue size in decimal and default is 1024.
+        --parse-ptype: Optional, set to use software to analyze packet type.
+                       Without this option, hardware will check the packet type.
+        [-L]|[-E]: L3fwd uses the parameters "-L" and "-E" to correspond to LPM and EM modes respectively.
+                   And the default is LPM mode.
+
+Common Steps
+------------
+1. Bind PF ports to kernel driver, i40e or ice, then create 1 VF from each PF,
+   take E810 for example::
+
+    <dpdk_dir>#echo 1 > /sys/bus/pci/devices/0000\:17\:00.0/sriov_numvfs
+
+   Set vf mac address::
+
+    <dpdk_dir>#ip link set ens5f0 vf 0 mac 00:12:34:56:78:01
+
+   Bind all the created VFs to vfio-pci::
+
+    <dpdk_dir>#./usertools/dpdk-devbind.py -s
+    0000:17:00.0 'Device 1592' if=ens5f0 drv=ice unused=vfio-pci
+    0000:17:01.0 'Device 1592' if=ens5f0v0 drv=iavf unused=vfio-pci
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci <pci device id>
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci 0000:17:01.0
+
+2. Configure traffic generator to send traffic
+
+    Routing table for IPv4 packets
+        - In LPM mode, the LPM table used for packet routing is:
+
+        +-------+-----------------------+
+        |   #   | LPM prefix (IP/length)|
+        +=======+=======================+
+        |   0   |      198.18.0.0/24    |
+        +-------+-----------------------+
+        |   1   |      198.18.1.0/24    |
+        +-------+-----------------------+
+        |   2   |      198.18.2.0/24    |
+        +-------+-----------------------+
+        |   3   |      198.18.3.0/24    |
+        +-------+-----------------------+
+
+    The flows need to be configured and started by the traffic generator:
+        - IPv4 packets
+
+        +------+---------+------------+---------+
+        | Flow | Traffic | IPv4       | IPv4    |
+        |      | Gen.    | Dst.       | Src.    |
+        |      | Port    | Address    | Address |
+        +======+=========+============+=========+
+        |   1  |   TG0   | 198.18.1.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   2  |   TG1   | 198.18.0.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   3  |   TG2   | 198.18.3.1 |  Any Ip |
+        +------+---------+------------+---------+
+        |   4  |   TG3   | 198.18.2.1 |  Any Ip |
+        +------+---------+------------+---------+
+
+        Set the packet length : 64 bytes-1518 bytes
+        The IPV4 Src Address increase with the num 1024.
+
+3. Test result table
+
+    +-----------+------------+-------------+---------+
+    |  Fwd_core | Frame Size |  Throughput |   Rate  |
+    +===========+============+=============+=========+
+    |  1C/1T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  1C/1T    |   ...      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    64      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+
+
+Test Case: test_perf_vf_rfc2544_ipv4_lpm
+----------------------------------------
+
+1. Bind VF ports to dpdk driver as common step 1.
+
+2. Launch l3fwd::
+
+     <build_dir>/examples/dpdk-l3fwd -l 5-8 -n 8 --force-max-simd-bitwidth=512 \
+     -- -p 0x1 --config "(0,0,5),(0,1,6),(0,2,7),(0,3,8)" --rx-queue-size 1024 \
+     --tx-queue-size 1024 --parse-ptype
+
+3. Configure traffic generator to send traffic as common step 2.
+
+4. Record Test results as common step 3.
-- 
2.34.1

[dts][PATCH V1 8/9]test_plans: add vf_l3fwd_lpm_ipv6_kernelpf test plan

[Yingya Han]

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 .../vf_l3fwd_lpm_ipv6_kernelpf_test_plan.rst  | 159 ++++++++++++++++++
 1 file changed, 159 insertions(+)
 create mode 100644 test_plans/vf_l3fwd_lpm_ipv6_kernelpf_test_plan.rst

diff --git a/test_plans/vf_l3fwd_lpm_ipv6_kernelpf_test_plan.rst b/test_plans/vf_l3fwd_lpm_ipv6_kernelpf_test_plan.rst
new file mode 100644
index 00000000..17f02b98
--- /dev/null
+++ b/test_plans/vf_l3fwd_lpm_ipv6_kernelpf_test_plan.rst
@@ -0,0 +1,159 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+   Copyright(c) 2022 Intel Corporation
+
+=============================================================
+VF L3 forwarding kernel PF test in LPM mode with IPV6 packets
+=============================================================
+
+This document provides benchmark test for NIC VFs which are created from
+kernel PFs or. These tests use l3fwd as a simple forwarder between NIC vfs.
+The goal of this test plan is to have a tested benchmark between NIC vfs.
+The Layer-3 Forwarding  performance results are produced using ``l3fwd`` application.
+For detail test plan, please refer to ``l3fwd_test_plan.rst``.
+
+Prerequisites
+=============
+
+Topology
+--------
+It requires at least 1 port connected traffic generator::
+        Port0 --- TG0
+
+2 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+
+4 ports::
+        Port0 --- TG0
+        Port1 --- TG1
+        Port2 --- TG2
+        Port3 --- TG3
+
+Hardware
+--------
+This suite focus on l3fwd application, so any standard Ethernet Network Adapter is qualified.
+
+Software
+--------
+dpdk: git clone http://dpdk.org/git/dpdk
+trex: git clone http://trex-tgn.cisco.com/trex/release/v2.93.tar.gz
+
+
+Test Case
+=========
+The test case check the throughput result with lpm mode and ipv6, in the case,
+we will send the bi-direction flows with line rate, then we can check the passthrough rate.
+
+The l3fwd application has a number of command line options, here list the key options will be tested::
+
+    ./dpdk-l3fwd [EAL options] -- -p PORTMASK
+                             [--force-max-simd-bitwidth=max-simd-bitwidth]
+                             --config(port,queue,lcore)[,(port,queue,lcore)]
+                             [--rx-queue-size NPKTS]
+                             [--tx-queue-size NPKTS]
+                             [--parse-ptype]
+                             [-L]|[-E]
+                             ...
+    Note:
+        --force-max-simd-bitwidth: This setting is used to determine the vector path for component selection.
+                                   And the default is avx2.
+        --rx-queue-size: Rx queue size in decimal and default is 1024.
+        --tx-queue-size: Tx queue size in decimal and default is 1024.
+        --parse-ptype: Optional, set to use software to analyze packet type.
+                       Without this option, hardware will check the packet type.
+        [-L]|[-E]: L3fwd uses the parameters "-L" and "-E" to correspond to LPM and EM modes respectively.
+                   And the default is LPM mode.
+
+Common Steps
+------------
+1. Bind PF ports to kernel driver, i40e or ice, then create 1 VF from each PF,
+   take E810 for example::
+
+    <dpdk_dir>#echo 1 > /sys/bus/pci/devices/0000\:17\:00.0/sriov_numvfs
+
+   Set vf mac address::
+
+    <dpdk_dir>#ip link set ens5f0 vf 0 mac 00:12:34:56:78:01
+
+   Bind all the created VFs to vfio-pci::
+
+    <dpdk_dir>#./usertools/dpdk-devbind.py -s
+    0000:17:00.0 'Device 1592' if=ens5f0 drv=ice unused=vfio-pci
+    0000:17:01.0 'Device 1592' if=ens5f0v0 drv=iavf unused=vfio-pci
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci <pci device id>
+    <dpdk_dir>#./usertools/dpdk-devbind.py -b vfio-pci 0000:17:01.0
+
+2. Configure traffic generator to send traffic
+
+    Routing table for IPv6 packets
+        - In LPM mode, the LPM table used for packet routing is:
+
+        +-------+--------------------------------------------+
+        |   #   |           LPM prefix (IP/length)           |
+        +=======+============================================+
+        |   0   | 2001:0200:0000:0000:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+        |   1   | 2001:0200:0000:0001:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+        |   2   | 2001:0200:0000:0002:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+        |   3   | 2001:0200:0000:0003:0000:0000:0000:0000/64 |
+        +-------+--------------------------------------------+
+
+    The flows need to be configured and started by the traffic generator:
+        - IPv6 packets
+
+        +------+---------+-----------------------------------------+---------+
+        | Flow | Traffic |                                         | IPv6    |
+        |      | Gen.    |           IPV6 Dst. Address             | Src.    |
+        |      | Port    |                                         | Address |
+        +======+=========+=========================================+=========+
+        |   1  |   TG0   | 2001:0200:0000:0000:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   2  |   TG1   | 2001:0200:0000:0001:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   3  |   TG2   | 2001:0200:0000:0002:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+        |   4  |   TG3   | 2001:0200:0000:0003:0000:0000:0000:0000 |  Any Ip |
+        +------+---------+-----------------------------------------+---------+
+
+        Set the packet length : 66 bytes-1518 bytes
+        The IPV6 Src Address increase with the num 1024.
+
+3. Test result table
+
+    +-----------+------------+-------------+---------+
+    |  Fwd_core | Frame Size |  Throughput |   Rate  |
+    +===========+============+=============+=========+
+    |  1C/1T    |    66      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  1C/1T    |   ...      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    66      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  2C/2T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    66      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  4C/4T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    66      |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+    |  8C/8T    |    ...     |  xxxxx Mpps |   xxx % |
+    +-----------+------------+-------------+---------+
+
+
+Test Case: test_perf_vf_throughput_ipv6_lpm
+-------------------------------------------
+
+1. Bind VF ports to dpdk driver as common step 1.
+
+2. Launch l3fwd::
+
+     <build_dir>/examples/dpdk-l3fwd -l 5-8 -n 8 --force-max-simd-bitwidth=512 \
+     -- -p 0x1 --config "(0,0,5),(0,1,6),(0,2,7),(0,3,8)" --rx-queue-size 1024 \
+     --tx-queue-size 1024 --parse-ptype
+
+3. Configure traffic generator to send traffic as common step 2.
+
+4. Record Test results as common step 3.
-- 
2.34.1

[dts][PATCH V1 9/9]test_plans: add the index of test plan

[Yingya Han]

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 test_plans/index.rst | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/test_plans/index.rst b/test_plans/index.rst
index 9ca954e2..06404d2f 100644
--- a/test_plans/index.rst
+++ b/test_plans/index.rst
@@ -98,7 +98,9 @@ The following are the test plans for the DPDK DTS automated test system.
     l2fwd_test_plan
     l2tp_esp_coverage_test_plan
     l3fwd_test_plan
-    l3fwd_lpm_ipv4_test_plan.rst
+    l3fwd_lpm_ipv4_test_plan
+    l3fwd_lpm_ipv4_rfc2544_test_plan
+    l3fwd_lpm_ipv6_test_plan
     l3fwd_func_test_plan
     l3fwdacl_test_plan
     large_vf_test_plan
@@ -157,6 +159,7 @@ The following are the test plans for the DPDK DTS automated test system.
     eventdev_pipeline_test_plan
     tso_test_plan
     tx_preparation_test_plan
+    testpmd_perf_test_plan
     uni_pkt_test_plan
     userspace_ethtool_test_plan
     vlan_ethertype_config_test_plan
@@ -187,6 +190,11 @@ The following are the test plans for the DPDK DTS automated test system.
     vf_smoke_test_plan
     vf_to_vf_nic_bridge_test_plan
     vf_vlan_test_plan
+    vf_l3fwd_kernelpf_test_plan
+    vf_l3fwd_em_kernelpf_test_plan
+    vf_l3fwd_lpm_ipv4_kernelpf_test_plan
+    vf_l3fwd_lpm_ipv4_rfc2544_kernelpf_test_plan
+    vf_l3fwd_lpm_ipv6_kernelpf_test_plan
     kernelpf_iavf_test_plan
     vhost_multi_queue_qemu_test_plan
     vhost_qemu_mtu_test_plan
-- 
2.34.1

RE: [dts][PATCH V1 9/9]test_plans: add the index of test plan

[Chu, Haijun]

Acked-by: Haijun Chu<haijun.chu@intel.com>

-----Original Message-----
From: Yingya Han <yingyax.han@intel.com> 
Sent: Tuesday, January 3, 2023 4:40 PM
To: dts@dpdk.org
Cc: Han, YingyaX <yingyax.han@intel.com>
Subject: [dts][PATCH V1 9/9]test_plans: add the index of test plan

Signed-off-by: Yingya Han <yingyax.han@intel.com>
---
 

[dts][PATCH V1 8/9]test_plans: add vf_l3fwd_lpm_ipv6_kernelpf test plan

[lijuan.tu]

On Tue,  3 Jan 2023 08:39:50 +0000, Yingya Han <yingyax.han@intel.com> wrote:
> Signed-off-by: Yingya Han <yingyax.han@intel.com>

Acked-by: Lijuan Tu <lijuan.tu@intel.com>
Series applied, thanks