[dts][PATCH V1] test_plans/runtime_vf_queue_number: adjust test plan format

[dts][PATCH V1] test_plans/runtime_vf_queue_number: adjust test plan format

[Yaqi Tang]

Adjust the format of test plan according to test plan template,
and modify test case 1 vf to VF.

Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>
---
 .../runtime_vf_queue_number_test_plan.rst     | 272 +++++++++---------
 1 file changed, 138 insertions(+), 134 deletions(-)

diff --git a/test_plans/runtime_vf_queue_number_test_plan.rst b/test_plans/runtime_vf_queue_number_test_plan.rst
index 1d8dde99..b60ab2d4 100644
--- a/test_plans/runtime_vf_queue_number_test_plan.rst
+++ b/test_plans/runtime_vf_queue_number_test_plan.rst
@@ -1,10 +1,12 @@
 .. SPDX-License-Identifier: BSD-3-Clause
    Copyright(c) 2019 Intel Corporation
 
-====================================
+==================================
 VF Request Queue Number At Runtime
-====================================
+==================================
 
+Description
+===========
 Both kernel driver, I40E and DPDK PMD driver, igb_uio/vfio-pci support
 VF request queue number at runtime, that means the users could configure
 the VF queue number at runtime.
@@ -31,109 +33,112 @@ Please read all test plans to get complete information.
 Prerequisites
 =============
 
-1. Hardware:
-
--  Intel® Ethernet 700 Series(X710/XXV710/XL710)
-
-2. Software:
-
-- DPDK: http://dpdk.org/git/dpdk (version: 19.02+)
-- Scapy: http://www.secdev.org/projects/scapy/
-
-3. Scenario:
+topology
+--------
+.. figure:: image/2vf1pf.png
 
-- DPDK PF + DPDK VF
+Hardware
+--------
+Supported NICs: Intel® Ethernet 700 Series(X710/XXV710/XL710)
 
-4. test topology:
+Software
+--------
+dpdk: http://dpdk.org/git/dpdk (version: 19.02+)
+scapy: http://www.secdev.org/projects/scapy/
 
-.. figure:: image/2vf1pf.png
+Scenario
+--------
+DPDK PF + DPDK VF
 
 Set up scenario
-===============
+---------------
 
 Assume create 2 vf from 1pf.
 
 1. Bind PF to DPDK driver, igb_uio::
 
-     ./usertools/dpdk-devbind.py -b igb_uio 0000:18:00.0
+    ./usertools/dpdk-devbind.py -b igb_uio 0000:18:00.0
 
 2. Create 2 vf from PF::
 
-     echo 2 >/sys/bus/pci/devices/0000:18:00.0/max_vfs
+    echo 2 >/sys/bus/pci/devices/0000:18:00.0/max_vfs
 
-     usertools/dpdk-devbind.py --s
-     0000:18:00.0 'Ethernet Controller X710 for 10GbE SFP+' if= drv=igb_uio unused=i40e
-     0000:18:02.0 'XL710/X710 Virtual Function' unused=
+    usertools/dpdk-devbind.py --s
+    0000:18:00.0 'Ethernet Controller X710 for 10GbE SFP+' if= drv=igb_uio unused=i40e
+    0000:18:02.0 'XL710/X710 Virtual Function' unused=
 
 3. Detach VF from the host, bind them to vfio-pci driver::
 
-     modprobe vfio
-     modprobe vfio-pci
+    modprobe vfio
+    modprobe vfio-pci
 
    Note: there are 2 ways to bind devices to vfio-pci:
 
 - Leverage usertools in dpdk package::
 
-     usertools/dpdk-devbind.py --bind=vfio-pci 0000:18:02.0
+    usertools/dpdk-devbind.py --bind=vfio-pci 0000:18:02.0
 
 - leverage Linux command::
 
-     using `lspci -nn|grep -i ethernet` got VF device id, for example "8086 154c",
+    using `lspci -nn|grep -i ethernet` got VF device id, for example "8086 154c",
 
-     echo "8086 154c" > /sys/bus/pci/drivers/vfio-pci/new_id
-     echo 0000:18:02.0 > /sys/bus/pci/devices/0000:18:02.0/driver/unbind
-     echo 0000:18:02.0 > /sys/bus/pci/drivers/vfio-pci/bind
+    echo "8086 154c" > /sys/bus/pci/drivers/vfio-pci/new_id
+    echo 0000:18:02.0 > /sys/bus/pci/devices/0000:18:02.0/driver/unbind
+    echo 0000:18:02.0 > /sys/bus/pci/drivers/vfio-pci/bind
 
 4. Passthrough VFs 18:02.0 to vm0 and start vm0::
 
-     /usr/bin/qemu-system-x86_64  -name vm0 -enable-kvm \
-     -cpu host -smp 4 -m 2048 -drive file=/home/image/sriov-1.img -vnc :1 \
-     -device vfio-pci,host=0000:18:02.0,id=pt_0
+    /usr/bin/qemu-system-x86_64  -name vm0 -enable-kvm \
+    -cpu host -smp 4 -m 2048 -drive file=/home/image/sriov-1.img -vnc :1 \
+    -device vfio-pci,host=0000:18:02.0,id=pt_0
 
-Now the scenario has been set up, you will have 1 port in the vm0.
+   Now the scenario has been set up, you will have 1 port in the vm0.
 
 5. Bind VF to dpdk driver igb_uio in VM::
 
     usertools/dpdk-devbind.py --bind=igb_uio 0000:03:00.0
 
-Test case 1: reserve valid vf queue number
-==========================================
+Test case
+=========
+
+Test case 1: reserve valid VF queue number
+------------------------------------------
 
 1. Start PF testpmd with random queue-num-per-vf in [1, 2, 4, 8 ,16], for example, we use 4 as the reserved vf queue numbers::
 
-     ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0,queue-num-per-vf=4 \
-     --file-prefix=test1 --socket-mem 1024,1024 -- -i
+    ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0,queue-num-per-vf=4 \
+    --file-prefix=test1 --socket-mem 1024,1024 -- -i
 
    Note testpmd can be started normally without any wrong or error.
 
 2. Start VF testpmd::
 
-     ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 03:00.0 \
-     --file-prefix=test2 --socket-mem 1024,1024 -- -i
+    ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 03:00.0 \
+    --file-prefix=test2 --socket-mem 1024,1024 -- -i
 
 3. VF request a queue number that is equal to reserved queue number, and we can not find VF reset while confiuring it::
 
-     testpmd> port stop all
-     testpmd> port config all txq 4
-     testpmd> port config all rxq 4
-     testpmd> port start all
+    testpmd> port stop all
+    testpmd> port config all txq 4
+    testpmd> port config all rxq 4
+    testpmd> port start all
 
-   Start forwarding, you can see the actual queue number is 4, and there is no VF reset operation::
+4. Start forwarding, you can see the actual queue number is 4, and there is no VF reset operation::
 
-     testpmd> start
-     port 0: RX queue number: 4 Tx queue number: 4
+    testpmd> start
+    port 0: RX queue number: 4 Tx queue number: 4
 
-4. VF request a queue number that is greater than reserved queue number, and we find VF reset while confiuring it::
+5. VF request a queue number that is greater than reserved queue number, and we find VF reset while confiuring it::
 
-     testpmd> port stop all
-     testpmd> port config all txq 5
-     testpmd> port config all rxq 5
-     testpmd> port start all
+    testpmd> port stop all
+    testpmd> port config all txq 5
+    testpmd> port config all rxq 5
+    testpmd> port start all
 
-   Start forwarding, you can see the actual queue number is 5, and find VF reseted::
+6. Start forwarding, you can see the actual queue number is 5, and find VF reseted::
 
-     testpmd> start
-     port 0: RX queue number: 5 Tx queue number: 5
+    testpmd> start
+    port 0: RX queue number: 5 Tx queue number: 5
 
 Note: Please find the expected behavior with different queue-num-per-vf in table[1].
 
@@ -162,119 +167,119 @@ Note: Please find the expected behavior with different queue-num-per-vf in table
     +------------------+---------------------+--------------------+
 
 Test case 2: reserve invalid VF queue number
-============================================
+--------------------------------------------
 
 1. Start PF testpmd with random queue-num-per-vf in [0, 3, 5-7 , 9-15, 17], for example, we use 0 as the reserved vf queue numbers::
 
-     ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0,queue-num-per-vf=0 \
-     --file-prefix=test1 --socket-mem 1024,1024 -- -i
+    ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0,queue-num-per-vf=0 \
+    --file-prefix=test1 --socket-mem 1024,1024 -- -i
 
 2. Verify testpmd started with logs as below::
 
-     i40e_pf_parse_vf_queue_number_handler(): Wrong VF queue number = 0, it must be power of 2 and equal or less than 16 !, Now it is kept the value = 4
+    i40e_pf_parse_vf_queue_number_handler(): Wrong VF queue number = 0, it must be power of 2 and equal or less than 16 !, Now it is kept the value = 4
 
 Test case 3: set valid VF queue number in testpmd command-line options
-======================================================================
+----------------------------------------------------------------------
 
 1. Start PF testpmd::
 
-      ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0 \
-      --file-prefix=test1 --socket-mem 1024,1024 -- -i
+    ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0 \
+    --file-prefix=test1 --socket-mem 1024,1024 -- -i
 
 2. Start VF testpmd with "--rxq=[rxq] --txq=[txq]", and random valid values from 1 to 16, take 3 for example::
 
-     ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 18:02.0 --file-prefix=test2 \
-     --socket-mem 1024,1024 -- -i --rxq=3 --txq=3
+    ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 18:02.0 --file-prefix=test2 \
+    --socket-mem 1024,1024 -- -i --rxq=3 --txq=3
 
 3. Configure vf forwarding prerequisits and start forwarding::
 
-     testpmd> set promisc all off
-     testpmd> set fwd mac
+    testpmd> set promisc all off
+    testpmd> set fwd mac
 
 4. Start forwarding, and verfiy the queue number informantion. both the RX queue number and the TX queue number must be same as your configuration. Here is 3::
 
-     testpmd> start
+    testpmd> start
 
-     port 0: RX queue number: 3 Tx queue number: 3
+    port 0: RX queue number: 3 Tx queue number: 3
 
 5. Send packets to VF from tester, and make sure they match the default RSS rules, IPV4_UNKNOW, and will be distributed to all the queues that you configured, Here is 3::
 
-     pkt1 = Ether(dst="$vf_mac", src="$tester_mac")/IP(src="10.0.0.1",dst="192.168.0.1")/("X"*48)
-     pkt2 = Ether(dst="$vf_mac", src="$tester_mac")/IP(src="10.0.0.1",dst="192.168.0.2")/("X"*48)
-     pkt3 = Ether(dst="$vf_mac", src="$tester_mac")/IP(src="10.0.0.1",dst="192.168.0.3")/("X"*48)
+    pkt1 = Ether(dst="$vf_mac", src="$tester_mac")/IP(src="10.0.0.1",dst="192.168.0.1")/("X"*48)
+    pkt2 = Ether(dst="$vf_mac", src="$tester_mac")/IP(src="10.0.0.1",dst="192.168.0.2")/("X"*48)
+    pkt3 = Ether(dst="$vf_mac", src="$tester_mac")/IP(src="10.0.0.1",dst="192.168.0.3")/("X"*48)
 
 6. Stop forwarding, and check the queues statistics, every RX/TX queue must has 1 packet go through, and total 3 packets in uni-direction as well as 6 packets in bi-direction::
 
     testpmd> stop
 
-      ------- Forward Stats for RX Port= 0/Queue= 0 -> TX Port= 0/Queue= 0 -------
-      RX-packets: 1       TX-packets: 1       TX-dropped: 0
-      ------- Forward Stats for RX Port= 0/Queue= 1 -> TX Port= 0/Queue= 1 -------
-      RX-packets: 1              TX-packets: 1             TX-dropped: 0
-      ------- Forward Stats for RX Port= 0/Queue= 2 -> TX Port= 0/Queue= 2 -------
-      RX-packets: 1              TX-packets: 1             TX-dropped: 0
-      ---------------------- Forward statistics for port 0  ----------------------
-      RX-packets: 3      RX-dropped: 0     RX-total: 3
-      TX-packets: 3       TX-dropped: 0             TX-total: 3
-      ----------------------------------------------------------------------------
+    ------- Forward Stats for RX Port= 0/Queue= 0 -> TX Port= 0/Queue= 0 -------
+    RX-packets: 1       TX-packets: 1       TX-dropped: 0
+    ------- Forward Stats for RX Port= 0/Queue= 1 -> TX Port= 0/Queue= 1 -------
+    RX-packets: 1              TX-packets: 1             TX-dropped: 0
+    ------- Forward Stats for RX Port= 0/Queue= 2 -> TX Port= 0/Queue= 2 -------
+    RX-packets: 1              TX-packets: 1             TX-dropped: 0
+    ---------------------- Forward statistics for port 0  ----------------------
+    RX-packets: 3      RX-dropped: 0     RX-total: 3
+    TX-packets: 3       TX-dropped: 0             TX-total: 3
+    ----------------------------------------------------------------------------
 
 7. Repeat step 2 to 6 with the mininum queue number, 1, and the maximum queue number, 16.
 
 Test case 4: set invalid VF queue number in testpmd command-line options
-========================================================================
+------------------------------------------------------------------------
 
 1. Start PF testpmd::
 
-     ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0 \
-     --file-prefix=test1 --socket-mem 1024,1024 -- -i
+    ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0 \
+    --file-prefix=test1 --socket-mem 1024,1024 -- -i
 
-2. Start VF testpmd with "--rxq=0 --txq=0" ::
+2. Start VF testpmd with "--rxq=0 --txq=0"::
 
-     ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 18:02.0 --file-prefix=test2 \
-     --socket-mem 1024,1024 -- -i --rxq=0 --txq=0
+    ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 18:02.0 --file-prefix=test2 \
+    --socket-mem 1024,1024 -- -i --rxq=0 --txq=0
 
-   Verify testpmd exited with error as below::
+3. Verify testpmd exited with error as below::
 
     Either rx or tx queues should be non-zero
 
-3. Start VF testpmd with "--rxq=17 --txq=17" ::
+4. Start VF testpmd with "--rxq=17 --txq=17"::
 
-     ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 18:02.0 --file-prefix=test2 \
-     --socket-mem 1024,1024 -- -i --rxq=17 --txq=17
+    ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 18:02.0 --file-prefix=test2 \
+    --socket-mem 1024,1024 -- -i --rxq=17 --txq=17
 
-   Verify testpmd exited with error as below::
+5. Verify testpmd exited with error as below::
 
-     txq 17 invalid - must be >= 0 && <= 16
+    txq 17 invalid - must be >= 0 && <= 16
 
 Test case 5: set valid VF queue number with testpmd function command
-====================================================================
+--------------------------------------------------------------------
 
 1. Start PF testpmd::
 
-     ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0 \
-     --file-prefix=test1 --socket-mem 1024,1024 -- -i
+    ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0 \
+    --file-prefix=test1 --socket-mem 1024,1024 -- -i
 
 2. Start VF testpmd without setting "rxq" and "txq"::
 
-     ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 05:02.0 --file-prefix=test2 \
-     --socket-mem 1024,1024 -- -i
+    ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 05:02.0 --file-prefix=test2 \
+    --socket-mem 1024,1024 -- -i
 
 3. Configure vf forwarding prerequisits and start forwarding::
 
-     testpmd> set promisc all off
-     testpmd> set fwd mac
+    testpmd> set promisc all off
+    testpmd> set fwd mac
 
 4. Set rx queue number and tx queue number with random value range from 1 to 16 with testpmd function command, take 3 for example::
 
-     testpmd> port stop all
-     testpmd> port config all rxq 3
-     testpmd> port config all txq 3
-     testpmd> port start all
+    testpmd> port stop all
+    testpmd> port config all rxq 3
+    testpmd> port config all txq 3
+    testpmd> port start all
 
 5. Repeat step 4-7 of test case 3.
 
 Test case 6: set invalid VF queue number with testpmd function command
-======================================================================
+----------------------------------------------------------------------
 
 1. Start PF testpmd::
 
@@ -287,57 +292,56 @@ Test case 6: set invalid VF queue number with testpmd function command
      --socket-mem 1024,1024 -- -i
 
 
-3. Set rx queue number and tx queue number with 0 ::
+3. Set rx queue number and tx queue number with 0::
 
      testpmd> port stop all
      testpmd> port config all rxq 0
      testpmd> port config all txq 0
      testpmd> port start all
 
-4. Set rx queue number and tx queue number with 17 ::
+4. Set rx queue number and tx queue number with 17::
 
      testpmd> port stop all
      testpmd> port config all rxq 17
      testpmd> port config all txq 17
      testpmd> port start all
 
-Verify error information::
-
-     Fail: input rxq (17) can't be greater than max_rx_queues (16) of port 0
+5. Verify error information::
 
+    Fail: input rxq (17) can't be greater than max_rx_queues (16) of port 0
 
 Test case 7: Reserve VF queue number when VF bind to kernel driver
-==================================================================
+------------------------------------------------------------------
 
 1. bind vf to kernel driver iavf::
 
-     ./usertools/dpdk-devbind.py -b i40e 0000:18:02.0
+    ./usertools/dpdk-devbind.py -b i40e 0000:18:02.0
 
-2. Reserve VF queue number ::
+2. Reserve VF queue number::
 
-     ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0,queue-num-per-vf=2 \
-     --file-prefix=test1 --socket-mem 1024,1024 -- -i
+    ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 18:00.0,queue-num-per-vf=2 \
+    --file-prefix=test1 --socket-mem 1024,1024 -- -i
 
 3. Check the VF0 rxq and txq number is 2::
 
-     ethtool -S enp5s2
-     NIC statistics:
-          rx_bytes: 0
-          rx_unicast: 0
-          rx_multicast: 0
-          rx_broadcast: 0
-          rx_discards: 0
-          rx_unknown_protocol: 0
-          tx_bytes: 0
-          tx_unicast: 0
-          tx_multicast: 0
-          tx_broadcast: 0
-          tx_discards: 0
-          tx_errors: 0
-          tx-0.packets: 0
-          tx-0.bytes: 0
-          tx-1.packets: 0
-          tx-1.bytes: 0
-          rx-0.packets: 0
-          rx-0.bytes: 0
-          rx-1.packets: 0
+    ethtool -S enp5s2
+    NIC statistics:
+        rx_bytes: 0
+        rx_unicast: 0
+        rx_multicast: 0
+        rx_broadcast: 0
+        rx_discards: 0
+        rx_unknown_protocol: 0
+        tx_bytes: 0
+        tx_unicast: 0
+        tx_multicast: 0
+        tx_broadcast: 0
+        tx_discards: 0
+        tx_errors: 0
+        tx-0.packets: 0
+        tx-0.bytes: 0
+        tx-1.packets: 0
+        tx-1.bytes: 0
+        rx-0.packets: 0
+        rx-0.bytes: 0
+        rx-1.packets: 0
-- 
2.25.1

[dts][PATCH V1] test_plans/short_live: modify testpmd config param

[Yaqi Tang]

The tetspmd config param of the test plan is not match that of the test script, so modify test plan testpmd config param.
And adjust the format of test plan according to test plan template.

Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>
---
 test_plans/short_live_test_plan.rst | 85 +++++++++++++++++------------
 1 file changed, 49 insertions(+), 36 deletions(-)

diff --git a/test_plans/short_live_test_plan.rst b/test_plans/short_live_test_plan.rst
index 2f6c9cb1..e72287a0 100644
--- a/test_plans/short_live_test_plan.rst
+++ b/test_plans/short_live_test_plan.rst
@@ -5,11 +5,13 @@
 Short-lived Application Tests
 =============================
 
+Description
+===========
 This feature is to reduce application start-up time, and do more
 cleanup when exit so that it could rerun many times.
 
 Prerequisites
--------------
+=============
 
 To test this feature, need to use linux time and start testpmd by: create
 and mount hugepage, must create more hugepages so that could measure time more
@@ -27,16 +29,18 @@ Start testpmd using time::
         # echo quit | time ./app/dpdk-testpmd -c 0x3 -n 4 -- -i
 
 
-Test Case 1: basic fwd testing
+Test Case 1: Basic fwd testing
 ------------------------------
 
 1. Start testpmd::
 
       ./app/dpdk-testpmd -c 0x3 -n 4 -- -i
 
-2. Set fwd mac
-3. Send packet from pkg
-4. Check all packets could be fwd back
+2. Set fwd mac.
+
+3. Send packet from pkg.
+
+4. Check all packets could be fwd back.
 
 Test Case 2: Get start up time
 ------------------------------
@@ -45,8 +49,9 @@ Test Case 2: Get start up time
 
     echo quit | time ./app/dpdk-testpmd -c 0x3 -n 4 --huge-dir /mnt/huge -- -i
 
-2. Get the time stats of the startup
-3. Repeat step 1~2 for at least 5 times to get the average
+2. Get the time stats of the startup.
+
+3. Repeat step 1~2 for at least 5 times to get the average.
 
 Test Case 3: Clean up with Signal -- testpmd
 --------------------------------------------
@@ -58,69 +63,77 @@ Test Case 3: Clean up with Signal -- testpmd
 
 2. Start testpmd::
 
-    ./app/dpdk-testpmd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -i
+    ./app/dpdk-testpmd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -i --portmask=0x3
+
+3. Set fwd mac.
+
+4. Send packets from pkg.
+
+5. Check all packets could be fwd back.
 
-3. Set fwd mac
-4. Send packets from pkg
-5. Check all packets could be fwd back
 6. Kill the testpmd in shell using below commands alternately::
 
-      SIGINT:  pkill -2  dpdk-testpmd
-      SIGTERM: pkill -15 dpdk-testpmd
+    SIGINT:  pkill -2  dpdk-testpmd
+    SIGTERM: pkill -15 dpdk-testpmd
 
 7. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
 
-
 Test Case 4: Clean up with Signal -- l2fwd
 ------------------------------------------
 
-0. Build l2fwd example::
+1. Build l2fwd example::
 
     meson configure -Dexamples=l2fwd x86_64-native-linuxapp-gcc
     ninja -C x86_64-native-linuxapp-gcc
 
-1. Create 4G hugepages, so that could save times when repeat::
+2. Create 4G hugepages, so that could save times when repeat::
 
     echo 2048 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
     mount -t hugetlbfs hugetlbfs /mnt/huge1
 
-2. Start testpmd::
+3. Start testpmd::
 
-    ./examples/dpdk-l2fwd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -p 0x01
+    ./examples/dpdk-l2fwd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -p 0x03
 
-3. Set fwd mac
-4. Send packets from pkg
-5. Check all packets could be fwd back
-6. Kill the testpmd in shell using below commands alternately::
+4. Set fwd mac.
 
-      SIGINT:  pkill -2  dpdk-l2fwd
-      SIGTERM: pkill -15 dpdk-l2fwd
+5. Send packets from pkg.
 
-7. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
+6. Check all packets could be fwd back.
+
+7. Kill the testpmd in shell using below commands alternately::
+
+    SIGINT:  pkill -2  dpdk-l2fwd
+    SIGTERM: pkill -15 dpdk-l2fwd
+
+8. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
 
 Test Case 5: Clean up with Signal -- l3fwd
 ------------------------------------------
 
-0. Build l3fwd example::
+1. Build l3fwd example::
 
     meson configure -Dexamples=l3fwd x86_64-native-linuxapp-gcc
     ninja -C x86_64-native-linuxapp-gcc
 
-1. Create 4G hugepages, so that could save times when repeat::
+2. Create 4G hugepages, so that could save times when repeat::
 
       echo 2048 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
       mount -t hugetlbfs hugetlbfs /mnt/huge1
 
-2. Start testpmd::
+3. Start testpmd::
 
-     ./examples/dpdk-l3fwd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -p 0x01 --config="(0,0,1)"
+     ./examples/dpdk-l3fwd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -p 0x03 --config='(0,0,1),(1,0,2)' &
 
-3. Set fwd mac
-4. Send packets from pkg
-5. Check all packets could be fwd back
-6. Kill the testpmd in shell using below commands alternately::
+4. Set fwd mac.
 
-     SIGINT:  pkill -2  dpdk-l3fwd
-     SIGTERM: pkill -15 dpdk-l3fwd
+5. Send packets from pkg.
 
-7. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
+6. Check all packets could be fwd back.
+
+7. Kill the testpmd in shell using below commands alternately::
+
+    SIGINT:  pkill -2  dpdk-l3fwd
+    SIGTERM: pkill -15 dpdk-l3fwd
+
+8. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
-- 
2.25.1

[dts][PATCH V1] test_plans/short_live: modify testpmd config param

[lijuan.tu]

On Wed,  8 Jun 2022 04:50:29 +0000, Yaqi Tang <yaqi.tang@intel.com> wrote:
> The tetspmd config param of the test plan is not match that of the test script, so modify test plan testpmd config param.
> And adjust the format of test plan according to test plan template.
> 
> Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>


Applied, thanks

[dts][PATCH V1] test_plans/runtime_vf_queue_number: adjust test plan format

[lijuan.tu]

On Wed,  8 Jun 2022 04:50:28 +0000, Yaqi Tang <yaqi.tang@intel.com> wrote:
> Adjust the format of test plan according to test plan template,
> and modify test case 1 vf to VF.
> 
> Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>


Applied, thanks