[dts] [PATCH V2] test_plans:fix build warning

[dts] [PATCH V2] test_plans:fix build warning

[Wenjie Li]

fix build warning

Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
V2: fix "1 line adds whitespace errors."
0001-test_plans-fix-build-warning.patch:26: trailing whitespace.
   (b) Windriver TS 2 or CentOS 7 operating systems
warning: 1 line adds whitespace errors.


---
 test_plans/bbdev_test_plan.rst     |  6 +++++-
 test_plans/index.rst               |  7 ++++++-
 test_plans/sriov_kvm_test_plan.rst | 14 ++++++++++----
 3 files changed, 21 insertions(+), 6 deletions(-)

diff --git a/test_plans/bbdev_test_plan.rst b/test_plans/bbdev_test_plan.rst
index 800e7f6..7fa0e2a 100644
--- a/test_plans/bbdev_test_plan.rst
+++ b/test_plans/bbdev_test_plan.rst
@@ -67,12 +67,14 @@ Prerequisites
 =============
 
 1. OS and Hardware
+
    (a) An AVX2 supporting machine
-   (b) Windriver TS 2 or CentOS 7 operating systems
+   (b) Windriver TS 2 or CentOS 7 operating systems
        (Fedora 25 and Ubuntu 16.04 is ok.)
    (c) Intel ICC compiler installed
 
 2. FlexRAN SDK Libraries
+
    To build DPDK with the *turbo_sw* PMD the user is required to download
    the export controlled ``FlexRAN SDK`` Libraries.
    An account at Intel Resource Design Center needs to be registered from
@@ -84,6 +86,7 @@ Prerequisites
    You can refer to the file dpdk/doc/guides/bbdevs/turbo_sw.rst.
 
 3. PMD setting
+
    Current BBDEV framework is en-suited with two vdev PMD drivers:
    null and turbo_sw.
    1) Null PMD is similar to cryptodev Null PMD, which is an empty driver to
@@ -101,6 +104,7 @@ Prerequisites
    They are both located in the build configuration file ``common_base``.
 
 4. Test tool
+
    A test suite for BBDEV is packaged with the framework to ease the
    validation needs for various functions and use cases.
    The tool to use for validation and testing is called: test-bbdev,
diff --git a/test_plans/index.rst b/test_plans/index.rst
index 28f5a69..e15823e 100644
--- a/test_plans/index.rst
+++ b/test_plans/index.rst
@@ -133,6 +133,7 @@ The following are the test plans for the DPDK DTS automated test system.
     compressdev_qat_pmd_test_plan
     compressdev_zlib_pmd_test_plan
     enable_package_download_in_ice_driver_test_plan
+    multicast_test_plan
 
     veb_switch_test_plan
     vf_daemon_test_plan
@@ -151,7 +152,6 @@ The following are the test plans for the DPDK DTS automated test system.
     vhost_multi_queue_qemu_test_plan
     vhost_pmd_xstats_test_plan
     vhost_qemu_mtu_test_plan
-    vhost_tso_test_plan
     vhost_user_live_migration_test_plan
     vm_power_manager_test_plan
     vmdq_test_plan
@@ -230,3 +230,8 @@ The following are the test plans for the DPDK DTS automated test system.
     iavf_test_plan
     packet_capture_test_plan
     packet_ordering_test_plan
+    bbdev_test_plan
+    performance_thread_test_plan
+
+    fips_cryptodev_test_plan
+    flow_filtering_test_plan
\ No newline at end of file
diff --git a/test_plans/sriov_kvm_test_plan.rst b/test_plans/sriov_kvm_test_plan.rst
index f22b2ed..1b84f78 100644
--- a/test_plans/sriov_kvm_test_plan.rst
+++ b/test_plans/sriov_kvm_test_plan.rst
@@ -135,7 +135,7 @@ Send 10 packets with VF0 mac address and make sure the packets will be
 forwarded by VF1.
 
 Test Case2: Mirror Traffic between 2VMs with Pool up mirroring
-===========================================================
+==============================================================
 
 Set up common 2VM prerequisites.
 
@@ -216,7 +216,7 @@ After test need reset mirror rule::
     PF testpmd-> reset port 0 mirror-rule 0
 
 Test Case6: Mirror Traffic between 2VMs with Vlan mirroring
-==========================================================
+===========================================================
 
 Set up common 2VM prerequisites.
 
@@ -237,7 +237,7 @@ After test need reset mirror rule::
     PF testpmd-> reset port 0 mirror-rule 0
 
 Test Case7: Mirror Traffic between 2VMs with up link mirroring & down link mirroring
-==================================================================================
+====================================================================================
 
 Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts::
 
@@ -247,9 +247,12 @@ Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts::
 When mirroring only between two Vfs, pool up (or down) mirroring and up (or down) link mirroring lead
 to the same behavior, so we randomly choose one way to mirror in both up and down directions.
 up link mirroring as below:
+
    1. Pool up mirroring (Case 2)
    2. Uplink port mirroring(Case 4)
+
 down link mirroring as below:
+
    1. Pool down mirroring(Fortville only, Case 3)
    2. Downlink port mirroring(Case 5)
 
@@ -274,7 +277,7 @@ After test need reset mirror rule::
     PF testpmd-> reset port 0 mirror-rule 1
 
 Test Case8: Mirror Traffic between 2VMs with Vlan & with up link mirroring & down link mirroring
-=============================================================================================
+================================================================================================
 
 Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts::
 
@@ -284,9 +287,12 @@ Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts::
 When mirroring only between two Vfs, pool up (or down) mirroring and up (or down) link mirroring lead
 to the same behavior, so we randomly choose one way to mirror in both up and down directions.
 up link mirroring as below:
+
    1. Pool up mirroring (Case 2)
    2. Uplink port mirroring(Case 4)
+
 down link mirroring as below:
+
    1. Pool down mirroring(Fortville only, Case 3)
    2. Downlink port mirroring(Case 5)
 
-- 
2.17.2

Re: [dts] [PATCH V2] test_plans:fix build warning

[Tu, Lijuan]

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Monday, September 23, 2019 11:06 AM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V2] test_plans:fix build warning
> 
> fix build warning
> 
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> V2: fix "1 line adds whitespace errors."
> 0001-test_plans-fix-build-warning.patch:26: trailing whitespace.
>    (b) Windriver TS 2 or CentOS 7 operating systems
> warning: 1 line adds whitespace errors.
> 
> 
> ---
>  test_plans/bbdev_test_plan.rst     |  6 +++++-
>  test_plans/index.rst               |  7 ++++++-
>  test_plans/sriov_kvm_test_plan.rst | 14 ++++++++++----
>  3 files changed, 21 insertions(+), 6 deletions(-)
> 
> diff --git a/test_plans/bbdev_test_plan.rst b/test_plans/bbdev_test_plan.rst
> index 800e7f6..7fa0e2a 100644
> --- a/test_plans/bbdev_test_plan.rst
> +++ b/test_plans/bbdev_test_plan.rst
> @@ -67,12 +67,14 @@ Prerequisites
>  =============
> 
>  1. OS and Hardware
> +
>     (a) An AVX2 supporting machine
> -   (b) Windriver TS 2 or CentOS 7 operating systems
> +   (b) Windriver TS 2 or CentOS 7 operating systems
>         (Fedora 25 and Ubuntu 16.04 is ok.)
>     (c) Intel ICC compiler installed
> 
>  2. FlexRAN SDK Libraries
> +
>     To build DPDK with the *turbo_sw* PMD the user is required to download
>     the export controlled ``FlexRAN SDK`` Libraries.
>     An account at Intel Resource Design Center needs to be registered from
> @@ -84,6 +86,7 @@ Prerequisites
>     You can refer to the file dpdk/doc/guides/bbdevs/turbo_sw.rst.
> 
>  3. PMD setting
> +
>     Current BBDEV framework is en-suited with two vdev PMD drivers:
>     null and turbo_sw.
>     1) Null PMD is similar to cryptodev Null PMD, which is an empty driver to
> @@ -101,6 +104,7 @@ Prerequisites
>     They are both located in the build configuration file ``common_base``.
> 
>  4. Test tool
> +
>     A test suite for BBDEV is packaged with the framework to ease the
>     validation needs for various functions and use cases.
>     The tool to use for validation and testing is called: test-bbdev, diff --git
> a/test_plans/index.rst b/test_plans/index.rst index 28f5a69..e15823e 100644
> --- a/test_plans/index.rst
> +++ b/test_plans/index.rst
> @@ -133,6 +133,7 @@ The following are the test plans for the DPDK DTS
> automated test system.
>      compressdev_qat_pmd_test_plan
>      compressdev_zlib_pmd_test_plan
>      enable_package_download_in_ice_driver_test_plan
> +    multicast_test_plan
> 
>      veb_switch_test_plan
>      vf_daemon_test_plan
> @@ -151,7 +152,6 @@ The following are the test plans for the DPDK DTS
> automated test system.
>      vhost_multi_queue_qemu_test_plan
>      vhost_pmd_xstats_test_plan
>      vhost_qemu_mtu_test_plan
> -    vhost_tso_test_plan
>      vhost_user_live_migration_test_plan
>      vm_power_manager_test_plan
>      vmdq_test_plan
> @@ -230,3 +230,8 @@ The following are the test plans for the DPDK DTS
> automated test system.
>      iavf_test_plan
>      packet_capture_test_plan
>      packet_ordering_test_plan
> +    bbdev_test_plan
> +    performance_thread_test_plan
> +
> +    fips_cryptodev_test_plan
> +    flow_filtering_test_plan
> \ No newline at end of file
> diff --git a/test_plans/sriov_kvm_test_plan.rst
> b/test_plans/sriov_kvm_test_plan.rst
> index f22b2ed..1b84f78 100644
> --- a/test_plans/sriov_kvm_test_plan.rst
> +++ b/test_plans/sriov_kvm_test_plan.rst
> @@ -135,7 +135,7 @@ Send 10 packets with VF0 mac address and make
> sure the packets will be  forwarded by VF1.
> 
>  Test Case2: Mirror Traffic between 2VMs with Pool up mirroring -
> ===========================================================
> +==============================================================
> 
>  Set up common 2VM prerequisites.
> 
> @@ -216,7 +216,7 @@ After test need reset mirror rule::
>      PF testpmd-> reset port 0 mirror-rule 0
> 
>  Test Case6: Mirror Traffic between 2VMs with Vlan mirroring -
> ==========================================================
> +===========================================================
> 
>  Set up common 2VM prerequisites.
> 
> @@ -237,7 +237,7 @@ After test need reset mirror rule::
>      PF testpmd-> reset port 0 mirror-rule 0
> 
>  Test Case7: Mirror Traffic between 2VMs with up link mirroring & down link
> mirroring -
> ================================================================
> ==================
> +===============================================================
> ========
> +=============
> 
>  Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts::
> 
> @@ -247,9 +247,12 @@ Run testpmd on VM0 and VM1 and start traffic
> forward on the VM hosts::
>  When mirroring only between two Vfs, pool up (or down) mirroring and up
> (or down) link mirroring lead  to the same behavior, so we randomly choose
> one way to mirror in both up and down directions.
>  up link mirroring as below:
> +
>     1. Pool up mirroring (Case 2)
>     2. Uplink port mirroring(Case 4)
> +
>  down link mirroring as below:
> +
>     1. Pool down mirroring(Fortville only, Case 3)
>     2. Downlink port mirroring(Case 5)
> 
> @@ -274,7 +277,7 @@ After test need reset mirror rule::
>      PF testpmd-> reset port 0 mirror-rule 1
> 
>  Test Case8: Mirror Traffic between 2VMs with Vlan & with up link mirroring
> & down link mirroring -
> ================================================================
> =============================
> +===============================================================
> ========
> +=========================
> 
>  Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts::
> 
> @@ -284,9 +287,12 @@ Run testpmd on VM0 and VM1 and start traffic
> forward on the VM hosts::
>  When mirroring only between two Vfs, pool up (or down) mirroring and up
> (or down) link mirroring lead  to the same behavior, so we randomly choose
> one way to mirror in both up and down directions.
>  up link mirroring as below:
> +
>     1. Pool up mirroring (Case 2)
>     2. Uplink port mirroring(Case 4)
> +
>  down link mirroring as below:
> +
>     1. Pool down mirroring(Fortville only, Case 3)
>     2. Downlink port mirroring(Case 5)
> 
> --
> 2.17.2

Re: [dts] [PATCH V2 test_plans: fix build warning

[Tu, Lijuan]

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Monday, June 10, 2019 10:19 AM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V2 test_plans: fix build warning
> 
> fix build warings in test plans.
> 
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> V2: fix error: trailing whitespace
> 
>  test_plans/eventdev_perf_test_plan.rst |  6 ++---
>  test_plans/vhost_gro_test_plan.rst     | 31 +++++++++++++++++---------
>  2 files changed, 24 insertions(+), 13 deletions(-)
> 
> diff --git a/test_plans/eventdev_perf_test_plan.rst
> b/test_plans/eventdev_perf_test_plan.rst
> index ed1312a..520d635 100644
> --- a/test_plans/eventdev_perf_test_plan.rst
> +++ b/test_plans/eventdev_perf_test_plan.rst
> @@ -51,7 +51,8 @@ Description: Execute performance test with Atomic_atq
> type of stage in multi-flo
> 
>     # ./build/dpdk-test-eventdev -l 22-23 -w eventdev_device_bus_id -w
> device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --
> test=pipeline_atq --stlist=A --wlcores=23
> 
> -    Parameters:
> +    Parameters::
> +
>         -l CORELIST        : List of cores to run on
>                              The argument format is <c1>[-c2][,c3[-c4],...]
>                              where c1, c2, etc are core indexes between 0 and 24 @@ -
> 272,5 +273,4 @@ Description: Execute performance test with
> Ordered_queue type of stage in multi-
> 
>  2. Use Ixia to send huge number of packets(with same 5-tuple and different
> 5-tuple)
> 
> -3. Observe the speed of packets received(Rx-rate) on Ixia.
> -
> +3. Observe the speed of packets received(Rx-rate) on Ixia.
> \ No newline at end of file
> diff --git a/test_plans/vhost_gro_test_plan.rst
> b/test_plans/vhost_gro_test_plan.rst
> index a0ea3b9..e2652b3 100644
> --- a/test_plans/vhost_gro_test_plan.rst
> +++ b/test_plans/vhost_gro_test_plan.rst
> @@ -92,7 +92,9 @@ Test Case1: DPDK GRO lightmode test with tcp traffic
>      testpmd>port start 1
>      testpmd>start
> 
> -3.  Set up vm with virto device and using kernel virtio-net driver::
> +3.  Set up vm with virto device and using kernel virtio-net driver:
> +
> +  ::
> 
>      taskset -c 13 \
>      qemu-system-x86_64 -name us-vhost-vm1 \ @@ -145,7 +147,9 @@ Test
> Case2: DPDK GRO heavymode test with tcp traffic
>      testpmd>port start 1
>      testpmd>start
> 
> -3.  Set up vm with virto device and using kernel virtio-net driver::
> +3.  Set up vm with virto device and using kernel virtio-net driver:
> +
> +  ::
> 
>      taskset -c 13 \
>      qemu-system-x86_64 -name us-vhost-vm1 \ @@ -198,7 +202,9 @@ Test
> Case3: DPDK GRO heavymode_flush4 test with tcp traffic
>      testpmd>port start 1
>      testpmd>start
> 
> -3.  Set up vm with virto device and using kernel virtio-net driver::
> +3.  Set up vm with virto device and using kernel virtio-net driver:
> +
> +  ::
> 
>      taskset -c 13 \
>      qemu-system-x86_64 -name us-vhost-vm1 \ @@ -226,11 +232,14 @@
> Test Case4: DPDK GRO test with vxlan traffic
> 
>  Vxlan topology
>  --------------
> -  VM          Host
> -50.1.1.2      50.1.1.1
> -   |           |
> -1.1.2.3       1.1.2.4
> -   |------------Testpmd------------|
> +
> +::
> +
> +    VM          Host
> +  50.1.1.2      50.1.1.1
> +     |           |
> +  1.1.2.3       1.1.2.4
> +     |------------Testpmd------------|
> 
>  1. Connect two nic port directly, put nic2 into another namesapce and
> create Host VxLAN port::
> 
> @@ -269,7 +278,9 @@ Vxlan topology
>      testpmd>port start 1
>      testpmd>start
> 
> -3.  Set up vm with virto device and using kernel virtio-net driver::
> +3.  Set up vm with virto device and using kernel virtio-net driver:
> +
> +  ::
> 
>      taskset -c 13 \
>      qemu-system-x86_64 -name us-vhost-vm1 \ @@ -294,4 +305,4 @@ Vxlan
> topology  5. Start iperf test, run iperf server at vm side and iperf client at
> host side, check throughput in log::
> 
>      Host side :  ip netns exec t2 iperf -c 50.1.1.2 -i 2 -t 60 -f g -m
> -    VM side:     iperf -s -f g
> +    VM side:     iperf -s -f g
> \ No newline at end of file
> --
> 2.17.2

[dts] [PATCH V2 test_plans: fix build warning

[Wenjie Li]

fix build warings in test plans.

Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
---
V2: fix error: trailing whitespace

 test_plans/eventdev_perf_test_plan.rst |  6 ++---
 test_plans/vhost_gro_test_plan.rst     | 31 +++++++++++++++++---------
 2 files changed, 24 insertions(+), 13 deletions(-)

diff --git a/test_plans/eventdev_perf_test_plan.rst b/test_plans/eventdev_perf_test_plan.rst
index ed1312a..520d635 100644
--- a/test_plans/eventdev_perf_test_plan.rst
+++ b/test_plans/eventdev_perf_test_plan.rst
@@ -51,7 +51,8 @@ Description: Execute performance test with Atomic_atq type of stage in multi-flo
 
    # ./build/dpdk-test-eventdev -l 22-23 -w eventdev_device_bus_id -w device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=A --wlcores=23
 
-    Parameters:
+    Parameters::
+
        -l CORELIST        : List of cores to run on
                             The argument format is <c1>[-c2][,c3[-c4],...]
                             where c1, c2, etc are core indexes between 0 and 24
@@ -272,5 +273,4 @@ Description: Execute performance test with Ordered_queue type of stage in multi-
 
 2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
 
-3. Observe the speed of packets received(Rx-rate) on Ixia.
-
+3. Observe the speed of packets received(Rx-rate) on Ixia.
\ No newline at end of file
diff --git a/test_plans/vhost_gro_test_plan.rst b/test_plans/vhost_gro_test_plan.rst
index a0ea3b9..e2652b3 100644
--- a/test_plans/vhost_gro_test_plan.rst
+++ b/test_plans/vhost_gro_test_plan.rst
@@ -92,7 +92,9 @@ Test Case1: DPDK GRO lightmode test with tcp traffic
     testpmd>port start 1
     testpmd>start
 
-3.  Set up vm with virto device and using kernel virtio-net driver::
+3.  Set up vm with virto device and using kernel virtio-net driver:
+
+  ::
 
     taskset -c 13 \
     qemu-system-x86_64 -name us-vhost-vm1 \
@@ -145,7 +147,9 @@ Test Case2: DPDK GRO heavymode test with tcp traffic
     testpmd>port start 1
     testpmd>start
 
-3.  Set up vm with virto device and using kernel virtio-net driver::
+3.  Set up vm with virto device and using kernel virtio-net driver:
+
+  ::
 
     taskset -c 13 \
     qemu-system-x86_64 -name us-vhost-vm1 \
@@ -198,7 +202,9 @@ Test Case3: DPDK GRO heavymode_flush4 test with tcp traffic
     testpmd>port start 1
     testpmd>start
 
-3.  Set up vm with virto device and using kernel virtio-net driver::
+3.  Set up vm with virto device and using kernel virtio-net driver:
+
+  ::
 
     taskset -c 13 \
     qemu-system-x86_64 -name us-vhost-vm1 \
@@ -226,11 +232,14 @@ Test Case4: DPDK GRO test with vxlan traffic
 
 Vxlan topology
 --------------
-  VM          Host
-50.1.1.2      50.1.1.1
-   |           |
-1.1.2.3       1.1.2.4
-   |------------Testpmd------------|
+
+::
+
+    VM          Host
+  50.1.1.2      50.1.1.1
+     |           |
+  1.1.2.3       1.1.2.4
+     |------------Testpmd------------|
 
 1. Connect two nic port directly, put nic2 into another namesapce and create Host VxLAN port::
 
@@ -269,7 +278,9 @@ Vxlan topology
     testpmd>port start 1
     testpmd>start
 
-3.  Set up vm with virto device and using kernel virtio-net driver::
+3.  Set up vm with virto device and using kernel virtio-net driver:
+
+  ::
 
     taskset -c 13 \
     qemu-system-x86_64 -name us-vhost-vm1 \
@@ -294,4 +305,4 @@ Vxlan topology
 5. Start iperf test, run iperf server at vm side and iperf client at host side, check throughput in log::
 
     Host side :  ip netns exec t2 iperf -c 50.1.1.2 -i 2 -t 60 -f g -m
-    VM side:     iperf -s -f g
+    VM side:     iperf -s -f g
\ No newline at end of file
-- 
2.17.2