test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V2 test_plans: fix build warning
Date: Wed, 12 Jun 2019 02:46:50 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAB938B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1560133163-148531-1-git-send-email-wenjiex.a.li@intel.com>

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


  reply	other threads:[~2019-06-12  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10  2:19 Wenjie Li
2019-06-12  2:46 ` Tu, Lijuan [this message]
2019-09-23  3:05 [dts] [PATCH V2] test_plans:fix " Wenjie Li
2019-09-24  9:18 ` Tu, Lijuan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8CE3E05A3F976642AAB0F4675D0AD20E0BAB938B@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=wenjiex.a.li@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).