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

["Tu, Lijuan" <lijuan.tu@intel.com>]

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Friday, March 1, 2019 2:46 PM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V1] test_plans: fix build warning
> 
> fix build warning in these test_plans.
> 1. update the list in index.rst
> 2. fix the format
> 
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
>  test_plans/index.rst                          | 80 ++++++++++------
>  .../ipsec_gw_cryptodev_func_test_plan.rst     | 54 ++++++-----
>  test_plans/l2fwd_cryptodev_func_test_plan.rst | 94 ++++++++++---------
>  test_plans/pmd_bonded_8023ad_test_plan.rst    |  6 +-
>  ...host_single_core_performance_test_plan.rst | 12 +--
>   ...rtio_single_core_performance_test_plan.rst | 20 ++--
>  .../vlan_ethertype_config_test_plan.rst       |  2 +-
>  7 files changed, 149 insertions(+), 119 deletions(-)
> 
> diff --git a/test_plans/index.rst b/test_plans/index.rst index a114231..b7d155b
> 100644
> --- a/test_plans/index.rst
> +++ b/test_plans/index.rst
> @@ -42,57 +42,93 @@ The following are the test plans for the DPDK DTS
> automated test system.
>      checksum_offload_test_plan
>      cloud_filter_test_plan
>      coremask_test_plan
> -    crypto_perf_test_plan
> +    cryptodev_perf_crypto-perf_test_plan
> +    ddp_gtp_qregion_test_plan
> +    ddp_gtp_test_plan
> +    ddp_mpls_test_plan
> +    ddp_ppp_l2tp_test_plan
>      dual_vlan_test_plan
>      dynamic_config_test_plan
> +    dynamic_flowtype_test_plan
> +    dynamic_queue_test_plan
>      etag_test_plan
> +    external_memory_test_plan
>      external_mempool_handler_test_plan
>      fdir_test_plan
>      floating_veb_test_plan
> +    flow_classify_softnic_test_plan
>      fortville_rss_granularity_config_test_plan
>      ftag_test_plan
>      generic_filter_test_plan
> -    hotplug_test_plan
> +    generic_flow_api_test_plan
>      hotplug_mp_test_plan
> +    hotplug_test_plan
>      ieee1588_test_plan
> +    inline_ipsec_test_plan
>      interrupt_pmd_test_plan
> +    ip_pipeline_test_plan
>      ipfrag_test_plan
>      ipgre_test_plan
> -    ip_pipeline_test_plan
> +    ipsec_gw_cryptodev_func_test_plan
>      ipv4_reassembly_test_plan
> +    ixgbe_vf_get_extra_queue_information_test_plan
>      jumboframes_test_plan
>      kni_test_plan
> -    l2fwd_crypto_test_plan
> +    l2fwd_cryptodev_func_test_plan
>      l2fwd_test_plan
>      l3fwd_em_test_plan
>      l3fwd_test_plan
> +    l3fwdacl_test_plan
>      link_flowctrl_test_plan
>      link_status_interrupt_test_plan
> +    loopback_multi_paths_port_restart_performance_test_plan
> +    loopback_multi_paths_port_restart_test_plan
>      mac_filter_test_plan
>      macsec_for_ixgbe_test_plan
> -    mempool_exthandler_test_plan
> +    metering_and_policing_test_plan
> +    multiple_pthread_test_plan
>      NICStatistics_test_plan
>      nvgre_test_plan
> +    pmd_bonded_8023ad_test_plan
>      pmd_bonded_test_plan
> +    pmd_stacked_bonded_test_plan
> +    pmd_test_plan
>      pmdpcap_test_plan
>      pmdrss_hash_test_plan
>      pmdrssreta_test_plan
> -    pmd_test_plan
>      ptype_mapping_test_plan
> +    pvp_multi_paths_performance_test_plan
> +    pvp_multi_paths_vhost_single_core_performance_test_plan
> +    pvp_multi_paths_virtio_single_core_performance_test_plan
> +    qinq_filter_test_plan
> +    qos_api_test_plan
> +    qos_meter_test_plan
> +    qos_sched_test_plan
> +    queue_region_test_plan
>      queue_start_stop_test_plan
> +    rss_to_rte_flow_test_plan
> +    runtime_vf_queue_number_kernel_test_plan
> +    runtime_vf_queue_number_maxinum_test_plan
> +    runtime_vf_queue_number_test_plan
> +    rxtx_offload_test_plan
>      scatter_test_plan
>      short_live_test_plan
>      shutdown_api_test_plan
>      sriov_kvm_test_plan
>      stability_test_plan
> +    sw_eventdev_pipeline_sample_test_plan
>      tso_test_plan
>      tx_preparation_test_plan
>      uni_pkt_test_plan
>      userspace_ethtool_test_plan
> +    vlan_ethertype_config_test_plan
> +    vlan_test_plan
> +    vxlan_test_plan
>      veb_switch_test_plan
>      vf_daemon_test_plan
> -    vf_jumboframe_test_plan
>      vf_interrupt_pmd_test_plan
> +    vf_jumboframe_test_plan
> +    vf_kernel_test_plan
>      vf_macfilter_test_plan
>      vf_offload_test_plan
>      vf_packet_rxtx_test_plan
> @@ -101,45 +137,26 @@ The following are the test plans for the DPDK DTS
> automated test system.
>      vf_rss_test_plan
>      vf_to_vf_nic_bridge_test_plan
>      vf_vlan_test_plan
> +    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
>      virtio_1.0_test_plan
> -    vlan_ethertype_config_test_plan
> -    vlan_test_plan
> -    vmdq_test_plan
>      vm_power_manager_test_plan
> -    vxlan_test_plan
> -    ixgbe_vf_get_extra_queue_information_test_plan
> -    queue_region_test_plan
> -    inline_ipsec_test_plan
> -    sw_eventdev_pipeline_sample_test_plan
> -    dynamic_flowtype_test_plan
> -    vf_kernel_test_plan
> -    multiple_pthread_test_plan
> -    qinq_filter_test_plan
> -    generic_flow_api_test_plan
> -    rss_to_rte_flow_test_plan
> -    ddp_gtp_test_plan
> -    ddp_gtp_qregion_test_plan
> -    ddp_ppp_l2tp_test_plan
> -    ddp_mpls_test_plan
> -    runtime_queue_number_test_plan
> -    dynamic_queue_test_plan
> -    vhost_multi_queue_qemu_test_plan
> -    vhost_qemu_mtu_test_plan
> +    vmdq_test_plan
> 
>      unit_tests_cmdline_test_plan
>      unit_tests_crc_test_plan
> -    unit_tests_cryptodev_test_plan
> +    unit_tests_cryptodev_func_test_plan
>      unit_tests_dump_test_plan
>      unit_tests_eal_test_plan
>      unit_tests_kni_test_plan
> +    unit_tests_loopback_test_plan
>      unit_tests_lpm_test_plan
>      unit_tests_mbuf_test_plan
>      unit_tests_mempool_test_plan
>      unit_tests_pmd_perf_test_plan
> -    unit_tests_loopback_test_plan
>      unit_tests_power_test_plan
>      unit_tests_qos_test_plan
>      unit_tests_ringpmd_test_plan
> @@ -159,3 +176,4 @@ The following are the test plans for the DPDK DTS
> automated test system.
>      ptpclient_test_plan
>      distributor_test_plan
>      efd_test_plan
> +    example_build_test_plan
> diff --git a/test_plans/ipsec_gw_cryptodev_func_test_plan.rst
> b/test_plans/ipsec_gw_cryptodev_func_test_plan.rst
> index fd26fab..a103fac 100644
> --- a/test_plans/ipsec_gw_cryptodev_func_test_plan.rst
> +++ b/test_plans/ipsec_gw_cryptodev_func_test_plan.rst
> @@ -126,23 +126,25 @@ Prerequisites
> 
>  To test CryptoDev API, an example ipsec-secgw is added into DPDK.
> 
> -The test commands of ipsec-secgw is below:
> +The test commands of ipsec-secgw is below::
> 
> 
> -   ./build/ipsec-secgw [EAL options] --
> -                        -p PORTMASK -P -u PORTMASK -j FRAMESIZE
> -                        -l -w REPLAY_WINOW_SIZE -e -a
> -                        --config (port,queue,lcore)[,(port,queue,lcore]
> -                        --single-sa SAIDX
> -                        --rxoffload MASK
> -                        --txoffload MASK
> -                        -f CONFIG_FILE_PATH
> -compile the applications :
> +    ./build/ipsec-secgw [EAL options] --
> +        -p PORTMASK -P -u PORTMASK -j FRAMESIZE
> +        -l -w REPLAY_WINOW_SIZE -e -a
> +        --config (port,queue,lcore)[,(port,queue,lcore]
> +        --single-sa SAIDX
> +        --rxoffload MASK
> +        --txoffload MASK
> +        -f CONFIG_FILE_PATH
> +
> +compile the applications::
> 
>      make -C ./examples/ipsec-secgw
> 
> 
> -Configuration File Syntax
> +Configuration File Syntax:
> +
>      The ``-f CONFIG_FILE_PATH`` option enables the application read and
>      parse the configuration file specified, and configures the application
>      with a given set of SP, SA and Routing entries accordingly. The syntax of @@
> -196,10 +198,11 @@ Cryptodev AES-NI algorithm validation matrix is showed in
> table below.
>  | CIPHER_HASH | 3DES_CBC    | ENCRYPT     | 128         |  SHA1_HMAC  |
> GENERATE    |
>  +-------------+-------------+-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 2048,0 --legacy-
> mem -w 0000:60:00.0 -w 0000:60:00.2
> - --vdev crypto_aesni_mb_pmd_1 --vdev=crypto_aesni_mb_pmd_2 -l 9,10,11 -n
> 6  -- -P  --config "(0,0,10),(1,0,11)"
> --u 0x1 -p 0x3 -f /root/dts/local_conf/ipsec_test.cfg
> +    --vdev crypto_aesni_mb_pmd_1 --vdev=crypto_aesni_mb_pmd_2 -l 9,10,11 -
> n 6  -- -P  --config "(0,0,10),(1,0,11)"
> +    -u 0x1 -p 0x3 -f /root/dts/local_conf/ipsec_test.cfg
> 
>  Sub-case: QAT test case
>  ---------------------------
> @@ -226,10 +229,11 @@ Cryptodev QAT algorithm validation matrix is showed
> in table below.
>  | AEAD        | AES_GCM     | ENCRYPT     | 128         |
>  +-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 2048,0 --legacy-
> mem -w 0000:60:00.0 -w 0000:60:00.2 --w 0000:1a:01.0 -l 9,10,11 -n 6  -- -P  --
> config "(0,0,10),(1,0,11)" -u 0x1 -p 0x3 --f /root/dts/local_conf/ipsec_test.cfg
> +    -w 0000:1a:01.0 -l 9,10,11 -n 6  -- -P  --config "(0,0,10),(1,0,11)" -u 0x1 -p 0x3
> +    -f /root/dts/local_conf/ipsec_test.cfg
> 
>  Sub-case: AES-GCM test case
>  ------------------------------
> @@ -242,10 +246,11 @@ Cryptodev AES-GCM algorithm validation matrix is
> showed in table below.
>  | AEAD        | AES_GCM     | ENCRYPT     | 128         |
>  +-------------+-------------+-------------+-------------+
> 
> -example:
> -     ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 2048,0 --legacy-
> mem -w 0000:60:00.0 -w 0000:60:00.2
> ---vdev crypto_aesni_gcm_pmd_1 --vdev=crypto_aesni_gcm_pmd_2 -l 9,10,11 -
> n 6  -- -P  --config "(0,0,10),(1,0,11)"
> --u 0x1 -p 0x3 -f /root/dts/local_conf/ipsec_test.cfg
> +example::
> +
> +    ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 2048,0 --legacy-
> mem -w 0000:60:00.0 -w 0000:60:00.2
> +    --vdev crypto_aesni_gcm_pmd_1 --vdev=crypto_aesni_gcm_pmd_2 -l
> 9,10,11 -n 6  -- -P  --config "(0,0,10),(1,0,11)"
> +    -u 0x1 -p 0x3 -f /root/dts/local_conf/ipsec_test.cfg
> 
>  Sub-case: NULL test case
>  ------------------------------
> @@ -258,7 +263,8 @@ Cryptodev NULL algorithm validation matrix is showed
> in table below.
>  | CIPHER_HASH | NULL        | ENCRYPT     | 0           |  NULL       | GENERATE    |
>  +-------------+-------------+-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 2048,0 --legacy-
> mem -w 0000:60:00.0 -w 0000:60:00.2 ---vdev crypto_null_pmd_1 --
> vdev=crypto_null_pmd_2 -l 9,10,11 -n 6  -- -P  --config "(0,0,10),(1,0,11)"
> --u 0x1 -p 0x3 -f /root/dts/local_conf/ipsec_test.cfg
> \ No newline at end of file
> +    --vdev crypto_null_pmd_1 --vdev=crypto_null_pmd_2 -l 9,10,11 -n 6  -- -P  --
> config "(0,0,10),(1,0,11)"
> +    -u 0x1 -p 0x3 -f /root/dts/local_conf/ipsec_test.cfg
> diff --git a/test_plans/l2fwd_cryptodev_func_test_plan.rst
> b/test_plans/l2fwd_cryptodev_func_test_plan.rst
> index 27b90b9..4176770 100644
> --- a/test_plans/l2fwd_cryptodev_func_test_plan.rst
> +++ b/test_plans/l2fwd_cryptodev_func_test_plan.rst
> @@ -277,7 +277,7 @@ Prerequisites
> 
>  To test CryptoDev API, an example l2fwd-crypto is added into DPDK.
> 
> -The test commands of l2fwd-crypto is below:
> +The test commands of l2fwd-crypto is below::
> 
>      ./build/l2fwd-crypto [EAL options] -- [-p PORTMASK] [-q NQ] [-s] [-T PERIOD]
> /
>      [--cdev_type HW/SW/ANY] [--chain
> HASH_CIPHER/CIPHER_HASH/CIPHER_ONLY/HASH_ONLY/AEAD] / @@ -316,7
> +316,7 @@ correctly. The steps how to use ZUClibrary is described in DPDK code
> directory  dpdk/doc/guides/cryptodevs/zuc.rst.
> 
>  Test case: Cryptodev l2fwd test
> -=============================
> +===============================
> 
>  For function test, the DUT forward UDP packets generated by scapy.
> 
> @@ -334,7 +334,7 @@ and compare the payload with correct answer pre-
> stored in scripts::
>      |          | <-------------> |          |
>      +----------+                 +----------+
> 
> -compile the applications:
> +compile the applications::
> 
>      make -C ./examples/l2fwd-crypto
> 
> @@ -376,14 +376,15 @@ Cryptodev AES-NI algorithm validation matrix is
> showed in table below.
>  | CIPHER_HASH | 3DES_CBC    | ENCRYPT     | 128         |  SHA256_HMAC|
> GENERATE    |
>  +-------------+-------------+-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/l2fwd-crypto/build/l2fwd-crypto --socket-mem 1024,0 --legacy-
> mem -l 6,7,8 -n 2 ---vdev crypto_aesni_mb --vdev crypto_aesni_mb -- -p 0x1 --
> chain CIPHER_ONLY --cdev_type SW ---cipher_algo aes-cbc --cipher_op
> ENCRYPT --cipher_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> ---cipher_iv 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f --no-mac-
> updating
> +    --vdev crypto_aesni_mb --vdev crypto_aesni_mb -- -p 0x1 --chain
> CIPHER_ONLY --cdev_type SW
> +    --cipher_algo aes-cbc --cipher_op ENCRYPT --cipher_key
> 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> +    --cipher_iv 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> + --no-mac-updating
> 
>  Sub-case: QAT test case
> ----------------------------
> +-----------------------
> 
>  Cryptodev QAT algorithm validation matrix is showed in table below.
> 
> @@ -435,14 +436,15 @@ Cryptodev QAT algorithm validation matrix is showed
> in table below.
>  | AEAD        | AES_CCM     | ENCRYPT     | 128         |
>  +-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/l2fwd-crypto/build/l2fwd-crypto --socket-mem 1024,0 --legacy-
> mem -l 6,7,8 -n 2
> --- -p 0x1 --chain CIPHER_ONLY --cdev_type HW --cipher_algo aes-cbc --
> cipher_op ENCRYPT ---cipher_key
> 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> ---cipher_iv 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f --no-mac-
> updating
> +    -- -p 0x1 --chain CIPHER_ONLY --cdev_type HW --cipher_algo aes-cbc --
> cipher_op ENCRYPT
> +    --cipher_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> +    --cipher_iv 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> + --no-mac-updating
> 
>  Sub-case: OPENSSL test case
> ---------------------------
> +---------------------------
> 
>  Cryptodev OPENSSL algorithm validation matrix is showed in table below.
> 
> @@ -478,15 +480,16 @@ Cryptodev OPENSSL algorithm validation matrix is
> showed in table below.
>  | CIPHER_HASH | 3DES_CBC    | ENCRYPT     | 128         |  SHA256_HMAC|
> GENERATE    |
>  +-------------+-------------+-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/l2fwd-crypto/build/l2fwd-crypto --socket-mem 1024,0 --legacy-
> mem -l 6,7,8 -n 2 ---vdev crypto_openssl_pmd --vdev crypto_openssl_pmd -- -p
> 0x1 --chain CIPHER_ONLY ---cdev_type SW --cipher_algo aes-cbc --cipher_op
> ENCRYPT ---cipher_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> ---cipher_iv 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f --no-mac-
> updating
> +    --vdev crypto_openssl_pmd --vdev crypto_openssl_pmd -- -p 0x1 --chain
> CIPHER_ONLY
> +    --cdev_type SW --cipher_algo aes-cbc --cipher_op ENCRYPT
> +    --cipher_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> +    --cipher_iv 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> + --no-mac-updating
> 
>  Sub-case: QAT/SNOW3G Snow3G test case
> -------------------------------
> +-------------------------------------
> 
>  Cryptodev Snow3G algorithm validation matrix is showed in table below.
>  Cipher only, hash-only and chaining functionality is supported for Snow3g.
> @@ -503,14 +506,15 @@ Cipher only, hash-only and chaining functionality is
> supported for Snow3g.
>  | HASH_ONLY   | UIA2        | GENERATE    | 128         |
>  +-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/l2fwd-crypto/build/l2fwd-crypto --socket-mem 1024,0 --legacy-
> mem -l 6,7,8 -n 2
> --- -p 0x1 --chain HASH_ONLY --cdev_type HW --auth_algo snow3g-uia2 --
> auth_op GENERATE ---auth_key
> 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> ---auth_iv 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 --digest 4 --no-
> mac-updating
> +    -- -p 0x1 --chain HASH_ONLY --cdev_type HW --auth_algo snow3g-uia2 --
> auth_op GENERATE
> +    --auth_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> +    --auth_iv 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 --digest
> + 4 --no-mac-updating
> 
>  Sub-case: QAT/KASUMI Kasumi test case
> -------------------------------
> +-------------------------------------
> 
>  Cryptodev Kasumi algorithm validation matrix is showed in table below.
>  Cipher only, hash-only and chaining functionality is supported for Kasumi.
> @@ -527,14 +531,15 @@ Cipher only, hash-only and chaining functionality is
> supported for Kasumi.
>  | HASH_ONLY   | F9          | GENERATE    | 128         |
>  +-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/l2fwd-crypto/build/l2fwd-crypto --socket-mem 1024,0 --legacy-
> mem -l 6,7,8 -n 2 ---vdev crypto_kasumi_pmd --vdev crypto_kasumi_pmd -- -p
> 0x1 --chain HASH_ONLY --cdev_type SW ---auth_algo kasumi-f9 --auth_op
> GENERATE ---auth_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f --
> digest 4 --no-mac-updating
> +    --vdev crypto_kasumi_pmd --vdev crypto_kasumi_pmd -- -p 0x1 --chain
> HASH_ONLY --cdev_type SW
> +    --auth_algo kasumi-f9 --auth_op GENERATE
> +    --auth_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f --digest
> + 4 --no-mac-updating
> 
>  Sub-case: QAT/ZUC Zuc test case
> -------------------------------
> +-------------------------------
> 
>  Cryptodev ZUC algorithm validation matrix is showed in table below.
>  Cipher only, hash-only and chaining functionality is supported for ZUC.
> @@ -551,14 +556,15 @@ Cipher only, hash-only and chaining functionality is
> supported for ZUC.
>  | HASH_ONLY   | EIA3        | GENERATE    | 128         |
>  +-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/l2fwd-crypto/build/l2fwd-crypto --socket-mem 1024,0 --legacy-
> mem -l 6,7,8 -n 2 ---vdev crypto_zuc_pmd --vdev crypto_zuc_pmd -- -p 0x1 --
> chain HASH_ONLY --cdev_type SW ---auth_algo zuc-eia3 --auth_op GENERATE -
> -auth_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> ---auth_iv 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 --digest 4 --no-
> mac-updating
> +    --vdev crypto_zuc_pmd --vdev crypto_zuc_pmd -- -p 0x1 --chain HASH_ONLY
> --cdev_type SW
> +    --auth_algo zuc-eia3 --auth_op GENERATE --auth_key
> 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> +    --auth_iv 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 --digest
> + 4 --no-mac-updating
> 
>  Sub-case: AESNI-GCM test case
> ---------------------------
> +-----------------------------
> 
>  Cryptodev AESNI-GCM algorithm validation matrix is showed in table below.
> 
> @@ -578,15 +584,16 @@ Cryptodev AESNI-GCM algorithm validation matrix is
> showed in table below.
>  | CIPHER_HASH | AES-GMAC    | ENCRYPT     | 128         |  SHA256_HMAC|
> GENERATE    |
>  +-------------+-------------+-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/l2fwd-crypto/build/l2fwd-crypto --socket-mem 1024,0 --legacy-
> mem -l 6,7,8 -n 2 ---vdev crypto_aesni_gcm_pmd --vdev crypto_aesni_gcm_pmd
> -- -p 0x1 --chain AEAD --cdev_type SW ---aead_algo aes-gcm --aead_op
> ENCRYPT --aead_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> ---aead_iv 00:01:02:03:04:05:06:07:08:09:0a:0b --aad
> 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> ---digest 16 --no-mac-updating
> +    --vdev crypto_aesni_gcm_pmd --vdev crypto_aesni_gcm_pmd -- -p 0x1 --
> chain AEAD --cdev_type SW
> +    --aead_algo aes-gcm --aead_op ENCRYPT --aead_key
> 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> +    --aead_iv 00:01:02:03:04:05:06:07:08:09:0a:0b --aad
> 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f
> +    --digest 16 --no-mac-updating
> 
>  Sub-case: QAT/NULL null test case
> -------------------------------
> +---------------------------------
> 
>  Cryptodev NULL algorithm validation matrix is showed in table below.
>  Cipher only, hash-only and chaining functionality is supported for NULL.
> @@ -603,7 +610,8 @@ Cipher only, hash-only and chaining functionality is
> supported for NULL.
>  | HASH_ONLY   | NULL        | GENERATE    | 0           |
>  +-------------+-------------+-------------+-------------+
> 
> -example:
> +example::
> +
>      ./examples/l2fwd-crypto/build/l2fwd-crypto --socket-mem 2048,0 --legacy-
> mem -l 9,10,66 -n 6 ---vdev crypto_null_pmd --vdev crypto_null_pmd  --  -p 0x1 -
> -chain CIPHER_ONLY --cdev_type SW ---cipher_algo null --cipher_op ENCRYPT --
> no-mac-updating \ No newline at end of file
> +    --vdev crypto_null_pmd --vdev crypto_null_pmd  --  -p 0x1 --chain
> CIPHER_ONLY --cdev_type SW
> +    --cipher_algo null --cipher_op ENCRYPT --no-mac-updating
> diff --git a/test_plans/pmd_bonded_8023ad_test_plan.rst
> b/test_plans/pmd_bonded_8023ad_test_plan.rst
> index 03de918..4e45e08 100644
> --- a/test_plans/pmd_bonded_8023ad_test_plan.rst
> +++ b/test_plans/pmd_bonded_8023ad_test_plan.rst
> @@ -138,11 +138,9 @@ steps
> 
>  Test Case : basic behavior mac
>  ==============================
> -#. bonded device's default mac is one of each slave's mac after one slave has
> -   been added.
> +#. bonded device's default mac is one of each slave's mac after one slave has
> been added.
>  #. when no slave attached, mac should be 00:00:00:00:00:00 -#. slave's mac
> restore the MAC addresses that the slave has before they were -enslaved.
> +#. slave's mac restore the MAC addresses that the slave has before they were
> enslaved.
> 
>  steps
>  -----
> diff --git
> a/test_plans/pvp_multi_paths_vhost_single_core_performance_test_plan.rst
> b/test_plans/pvp_multi_paths_vhost_single_core_performance_test_plan.rst
> index 19b3096..247f162 100644
> --- a/test_plans/pvp_multi_paths_vhost_single_core_performance_test_plan.rst
> +++ b/test_plans/pvp_multi_paths_vhost_single_core_performance_test_plan
> +++ .rst
> @@ -30,9 +30,9 @@
>     ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
>     OF THE POSSIBILITY OF SUCH DAMAGE.
> 
> -=====================================
> +=======================================
>  PVP multi-paths vhost single core Tests -
> =====================================
> +=======================================
> 
>  Description
>  ===========
> @@ -43,7 +43,7 @@ no-mergeable, Virtio 1.1 mergeable, Virtio 1.1 no-
> mergeable Path.
>  For vhost single core test, give 2 cores for virtio and 1 core for vhost, use io fwd
> at virtio side to lower the virtio workload.
> 
>  Test Case 1: vhost single core performance test with Virtio 1.1 mergeable path -
> =================================================================
> ======
> +================================================================
> =======
> +=======
> 
>  flow:
>  TG --> NIC --> Virtio --> Vhost --> Virtio --> NIC --> TG @@ -67,7 +67,7 @@ TG -
> -> NIC --> Virtio --> Vhost --> Virtio --> NIC --> TG  3. Send packet with packet
> generator with different packet size, check the throughput.
> 
>  Test Case 2: vhost single core performance test with Virtio 1.1 no-mergeable
> path -
> =================================================================
> ======
> +================================================================
> =======
> +==========
> 
>  flow:
>  TG --> NIC --> Virtio --> Vhost --> Virtio --> NIC --> TG @@ -91,7 +91,7 @@ TG -
> -> NIC --> Virtio --> Vhost --> Virtio --> NIC --> TG  3. Send packet with packet
> generator with different packet size, check the throughput.
> 
>  Test Case 3: vhost single core performance test with Inorder mergeable path -
> =================================================================
> ======
> +================================================================
> =======
> +====
> 
>  flow:
>  TG --> NIC --> Virtio --> Vhost --> Virtio --> NIC --> TG @@ -115,7 +115,7 @@
> TG --> NIC --> Virtio --> Vhost --> Virtio --> NIC --> TG  3. Send packet with
> packet generator with different packet size, check the throughput.
> 
>  Test Case 4: vhost single core performance test with Inorder no-mergeable path
> -
> =================================================================
> ======
> +================================================================
> =======
> +=======
> 
>  flow:
>  TG --> NIC --> Virtio --> Vhost --> Virtio --> NIC --> TG diff --git
> a/test_plans/pvp_multi_paths_virtio_single_core_performance_test_plan.rst
> b/test_plans/pvp_multi_paths_virtio_single_core_performance_test_plan.rst
> index e9378bf..5c64d5d 100644
> --- a/test_plans/pvp_multi_paths_virtio_single_core_performance_test_plan.rst
> +++ b/test_plans/pvp_multi_paths_virtio_single_core_performance_test_pla
> +++ n.rst
> @@ -30,9 +30,9 @@
>     ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
>     OF THE POSSIBILITY OF SUCH DAMAGE.
> 
> -=====================================
> +========================================
>  PVP multi-paths virtio single core Tests -
> =====================================
> +========================================
> 
>  Description
>  ===========
> @@ -43,7 +43,7 @@ no-mergeable, Virtio 1.1 mergeable, Virtio 1.1 no-
> mergeable Path.
>  For virtio single core test,give 2 cores for vhost and 1 core for virtio, use io fwd
> at vhost side to lower the vhost workload.
> 
>  Test Case 1: virtio single core performance test with Virtio 1.1 mergeable path -
> =================================================================
> ======
> +================================================================
> =======
> +========
> 
>  flow:
>  TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG @@ -68,7 +68,7 @@ TG -
> -> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG  3. Send packet with packet
> generator with different packet size, check the throughput.
> 
>  Test Case 2: virtio single core performance test with Virtio 1.1 no-mergeable
> path -
> =================================================================
> ======
> +================================================================
> =======
> +===========
> 
>  flow:
>  TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG @@ -93,7 +93,7 @@ TG -
> -> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG  3. Send packet with packet
> generator with different packet size, check the throughput.
> 
>  Test Case 3: virtio single core performance test with Inorder mergeable path -
> =================================================================
> ======
> +================================================================
> =======
> +=====
> 
>  flow:
>  TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG @@ -118,7 +118,7 @@
> TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG  3. Send packet with
> packet generator with different packet size, check the throughput.
> 
>  Test Case 4: virtio single core performance test with Inorder no-mergeable path
> -
> =================================================================
> ======
> +================================================================
> =======
> +========
> 
>  flow:
>  TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG @@ -143,7 +143,7 @@
> TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG  3. Send packet with
> packet generator with different packet size, check the throughput.
> 
>  Test Case 5: virtio single core performance test with Mergeable path -
> =================================================================
> ======
> +================================================================
> ====
> 
>  flow:
>  TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG @@ -168,7 +168,7 @@
> TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG  3. Send packet with
> packet generator with different packet size, check the throughput.
> 
>  Test Case 6: virtio single core performance test with Normal path -
> =================================================================
> ======
> +================================================================
> =
> 
>  flow:
>  TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG @@ -193,7 +193,7 @@
> TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG  3. Send packet with
> packet generator with different packet size, check the throughput.
> 
>  Test Case 7: virtio single core performance test with Vector_RX path -
> =================================================================
> ======
> +================================================================
> ====
> 
>  flow:
>  TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG @@ -215,4 +215,4 @@
> TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
>      >set fwd mac
>      >start
> 
> -3. Send packet with packet generator with different packet size, check the
> throughput.
> \ No newline at end of file
> +3. Send packet with packet generator with different packet size, check the
> throughput.
> diff --git a/test_plans/vlan_ethertype_config_test_plan.rst
> b/test_plans/vlan_ethertype_config_test_plan.rst
> index 7096614..2462cf1 100644
> --- a/test_plans/vlan_ethertype_config_test_plan.rst
> +++ b/test_plans/vlan_ethertype_config_test_plan.rst
> @@ -142,7 +142,7 @@ Test Case 4: test VLAN header stripping with changing
> VLAN TPID
>        testpmd> vlan set outer tpid 0xA100 0
> 
>  4. Send 1 packet with VLAN TPID 0xA100 and VLAN Tag 16 on port ``A``.
> -  Verify that packet received in port ``B`` without VLAN Tag Identifier
> +   Verify that packet received in port ``B`` without VLAN Tag
> + Identifier
> 
>  5. Disable vlan header stripping on port ``0``::
> 
> --
> 2.17.2