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_vhost_single_core_performance_test_plan.rst
Date: Wed, 6 May 2020 03:25:34 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC21F2A@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200429215423.27490-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 5:54 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_vhost_single_core_performance_test_plan.rst
>
> From: Wang Yinan <yinan.wang@intel.com>
>
> Signed-off-by: Wang Yinan <yinan.wang@intel.com>
> ---
> ...ulti_paths_vhost_single_core_performance_test_plan.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git
> a/test_plans/pvp_multi_paths_vhost_single_core_performance_test_plan.rs
> t
> b/test_plans/pvp_multi_paths_vhost_single_core_performance_test_plan.rs
> t
> index 5306538..96445e8 100644
> ---
> a/test_plans/pvp_multi_paths_vhost_single_core_performance_test_plan.rs
> t
> +++
> b/test_plans/pvp_multi_paths_vhost_single_core_performance_test_plan
> +++ .rst
> @@ -164,7 +164,7 @@ Test Case 6: vhost single core performance test with
> non-mergeable path
>
> ./testpmd -l 7-9 -n 4 --file-prefix=virtio \
> --vdev=virtio_user0,mac=00:11:22:33:44:10,path=./vhost-
> net,queues=1,in_order=0,mrg_rxbuf=0,vectorized=1 \
> - -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=2 --
> txd=1024 --rxd=1024
> + -- -i --enable-hw-vlan-strip --rss-ip --nb-cores=2 --txd=1024
> + --rxd=1024
> >set fwd io
> >start
>
> @@ -185,7 +185,7 @@ Test Case 7: vhost single core performance test with
> vectorized_rx path
>
> ./testpmd -l 7-9 -n 4 --file-prefix=virtio \
> --vdev=virtio_user0,mac=00:11:22:33:44:10,path=./vhost-
> net,queues=1,in_order=0,mrg_rxbuf=0,vectorized=1 \
> - -- -i --tx-offloads=0x0 --nb-cores=2 --txd=1024 --rxd=1024
> + -- -i --nb-cores=2 --txd=1024 --rxd=1024
> >set fwd io
> >start
>
> @@ -226,8 +226,8 @@ Test Case 9: vhost single core performance test with
> virtio 1.1 inorder non-merg 2. Launch virtio-user by below command::
>
> ./testpmd -l 7-9 -n 4 --file-prefix=virtio \
> - --vdev=virtio_user0,mac=00:11:22:33:44:10,path=./vhost-
> net,queues=1,packed_vq=1,mrg_rxbuf=0,in_order=1,vectorized=1 \
> - -- -i --rx-offloads=0x10 --rss-ip --nb-cores=2 --txd=1024 --rxd=1024
> + --vdev=virtio_user0,mac=00:11:22:33:44:10,path=./vhost-
> net,queues=1,packed_vq=1,mrg_rxbuf=0,in_order=1,vectorized=0 \
> + -- -i --rss-ip --nb-cores=2 --txd=1024 --rxd=1024
> >set fwd io
> >start
>
> --
> 2.17.1
prev parent 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 21:54 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC21F2A@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).