test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Wang, Yinan" <yinan.wang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wang, Yinan" <yinan.wang@intel.com>
Subject: Re: [dts] [PATCH v1] test_plans: update test commonds for vectorized	cases in	pvp_multi_paths_virtio_single_core_performance_test_plan.rst
Date: Wed, 6 May 2020 03:25:48 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC21F65@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200429221226.27833-1-yinan.wang@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yinan
> Sent: Thursday, April 30, 2020 6:12 AM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>
> Subject: [dts] [PATCH v1] test_plans: update test commonds for vectorized
> cases in pvp_multi_paths_virtio_single_core_performance_test_plan.rst
> 
> From: Wang Yinan <yinan.wang@intel.com>
> 
> Signed-off-by: Wang Yinan <yinan.wang@intel.com>
> ---
>  ...lti_paths_virtio_single_core_performance_test_plan.rst | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> 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.rs
> t
> index 36d3a68..33731ee 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
> @@ -163,7 +163,7 @@ Test Case 6: virtio single core performance test with
> non-mergeable path
> 
>      ./testpmd -n 4 -l 5-6 --no-pci --file-prefix=virtio \
>      --vdev=net_virtio_user0,mac=00:01:02:03:04:05,path=./vhost-
> net,in_order=0,mrg_rxbuf=0,vectorized=1 \
> -    -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=1 --
> txd=1024 --rxd=1024
> +    -- -i --enable-hw-vlan-strip --rss-ip --nb-cores=1 --txd=1024
> + --rxd=1024
>      >set fwd mac
>      >start
> 
> @@ -184,7 +184,7 @@ Test Case 7: virtio single core performance test with
> vectorized_rx path
> 
>      ./testpmd -n 4 -l 5-6 --no-pci --file-prefix=virtio \
>      --vdev=net_virtio_user0,mac=00:01:02:03:04:05,path=./vhost-
> net,in_order=0,mrg_rxbuf=0,vectorized=1 \
> -    -- -i --tx-offloads=0x0 --nb-cores=1 --txd=1024 --rxd=1024
> +    -- -i --nb-cores=1 --txd=1024 --rxd=1024
>      >set fwd mac
>      >start
> 
> @@ -225,8 +225,8 @@ Test Case 9: virtio single core performance test with
> virtio 1.1 inorder non-mer  2. Launch virtio-user by below command::
> 
>      ./testpmd -n 4 -l 5-6 --no-pci --file-prefix=virtio \
> -    --vdev=net_virtio_user0,mac=00:01:02:03:04:05,path=./vhost-
> net,packed_vq=1,mrg_rxbuf=0,in_order=1,vectorized=1 \
> -    -- -i --rx-offloads=0x10 --rss-ip --nb-cores=1 --txd=1024 --rxd=1024
> +    --vdev=net_virtio_user0,mac=00:01:02:03:04:05,path=./vhost-
> net,packed_vq=1,mrg_rxbuf=0,in_order=1,vectorized=0 \
> +    -- -i --rss-ip --nb-cores=1 --txd=1024 --rxd=1024
>      >set fwd mac
>      >start
> 
> --
> 2.17.1


      reply	other threads:[~2020-05-06  3:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 22:12 Yinan
2020-05-06  3:25 ` Tu, Lijuan [this message]

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=8CE3E05A3F976642AAB0F4675D0AD20E0BC21F65@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yinan.wang@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).