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: add packed ring vectorized cases in pvp_multi_paths_virtio_single_core_performance_test_plan
Date: Mon, 27 Apr 2020 07:51:09 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC12A99@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200425214258.444-1-yinan.wang@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yinan
> Sent: Sunday, April 26, 2020 5:43 AM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>
> Subject: [dts] [PATCH v1] test_plans: add packed ring vectorized cases in
> pvp_multi_paths_virtio_single_core_performance_test_plan
>
> From: Wang Yinan <yinan.wang@intel.com>
>
> Signed-off-by: Wang Yinan <yinan.wang@intel.com>
> ---
> ...rtio_single_core_performance_test_plan.rst | 60 +++++++------------
> 1 file changed, 23 insertions(+), 37 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 596d1e9..36d3a68 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
> @@ -38,10 +38,6 @@ Benchmark PVP virtio single core performance with 10
> tx/rx paths. Includes merge inorder mergeable, inorder non-mergeable,
> virtio 1.1 mergeable, virtio 1.1 non-mergeable，virtio 1.1 inorder mergeable,
> virtio 1.1 inorder non-mergeable, virtio1.1 vectorized path.
> Give 2 cores for vhost and 1 core for virtio, set io fwd at vhost side to lower
> the vhost workload.
> -Note: Virtio 1.1 vectorizedized path need below three initial requirements:
> - 1. AVX512 is allowed in config file and supported by compiler
> - 2. Host cpu support AVX512F
> - 3. ring size is power of two
>
> Test flow
> =========
> @@ -54,15 +50,13 @@ Test Case 1: virtio single core performance test with
> virtio 1.1 mergeable path 1. Bind one port to igb_uio, then launch vhost by
> below command::
>
> rm -rf vhost-net*
> - ./testpmd -n 4 -l 2-4 --socket-mem 1024,1024 --legacy-mem \
> - --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' -
> - -i --nb-cores=2 --txd=1024 --rxd=1024
> + ./testpmd -n 4 -l 2-4 --file-prefix=vhost --vdev
> + 'net_vhost0,iface=vhost-net,queues=1,client=0' -- -i --nb-cores=2
> + --txd=1024 --rxd=1024
> testpmd>set fwd io
> testpmd>start
>
> 2. Launch virtio-user by below command::
>
> - ./testpmd -n 4 -l 5-6 --socket-mem 1024,1024 \
> - --legacy-mem --no-pci --file-prefix=virtio \
> + ./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=1,in_order=0 \
> -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=1 --
> txd=1024 --rxd=1024
> >set fwd mac
> @@ -76,15 +70,14 @@ Test Case 2: virtio single core performance test with
> virtio 1.1 non-mergeable p 1. Bind one port to igb_uio, then launch vhost by
> below command::
>
> rm -rf vhost-net*
> - ./testpmd -n 4 -l 2-4 --socket-mem 1024,1024 --legacy-mem \
> + ./testpmd -n 4 -l 2-4 \
> --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' --
> -i --nb-cores=2 --txd=1024 --rxd=1024
> testpmd>set fwd io
> testpmd>start
>
> 2. Launch virtio-user by below command::
>
> - ./testpmd -n 4 -l 5-6 --socket-mem 1024,1024 \
> - --legacy-mem --no-pci --file-prefix=virtio \
> + ./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=0 \
> -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=1 --
> txd=1024 --rxd=1024
> >set fwd mac
> @@ -98,15 +91,14 @@ Test Case 3: virtio single core performance test with
> inorder mergeable path 1. Bind one port to igb_uio, then launch vhost by
> below command::
>
> rm -rf vhost-net*
> - ./testpmd -n 4 -l 2-4 --socket-mem 1024,1024 --legacy-mem \
> + ./testpmd -n 4 -l 2-4 \
> --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' --
> -i --nb-cores=2 --txd=1024 --rxd=1024
> testpmd>set fwd io
> testpmd>start
>
> 2. Launch virtio-user by below command::
>
> - ./testpmd -n 4 -l 5-6 --socket-mem 1024,1024 \
> - --legacy-mem --no-pci --file-prefix=virtio \
> + ./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=1,mrg_rxbuf=1 \
> -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=1 --
> txd=1024 --rxd=1024
> >set fwd mac
> @@ -120,15 +112,14 @@ Test Case 4: virtio single core performance test
> with inorder non-mergeable path 1. Bind one port to igb_uio, then launch
> vhost by below command::
>
> rm -rf vhost-net*
> - ./testpmd -n 4 -l 2-4 --socket-mem 1024,1024 --legacy-mem \
> + ./testpmd -n 4 -l 2-4 \
> --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' --
> -i --nb-cores=2 --txd=1024 --rxd=1024
> testpmd>set fwd io
> testpmd>start
>
> 2. Launch virtio-user by below command::
>
> - ./testpmd -n 4 -l 5-6 --socket-mem 1024,1024 \
> - --legacy-mem --no-pci --file-prefix=virtio \
> + ./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=1,mrg_rxbuf=0 \
> -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=1 --
> txd=1024 --rxd=1024
> >set fwd mac
> @@ -142,15 +133,14 @@ Test Case 5: virtio single core performance test
> with mergeable path 1. Bind one port to igb_uio, then launch vhost by below
> command::
>
> rm -rf vhost-net*
> - ./testpmd -n 4 -l 2-4 --socket-mem 1024,1024 --legacy-mem \
> + ./testpmd -n 4 -l 2-4 \
> --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' --
> -i --nb-cores=2 --txd=1024 --rxd=1024
> testpmd>set fwd io
> testpmd>start
>
> 2. Launch virtio-user by below command::
>
> - ./testpmd -n 4 -l 5-6 --socket-mem 1024,1024 \
> - --legacy-mem --no-pci --file-prefix=virtio \
> + ./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=1 \
> -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=1 --
> txd=1024 --rxd=1024
> >set fwd mac
> @@ -164,16 +154,15 @@ Test Case 6: virtio single core performance test
> with non-mergeable path 1. Bind one port to igb_uio, then launch vhost by
> below command::
>
> rm -rf vhost-net*
> - ./testpmd -n 4 -l 2-4 --socket-mem 1024,1024 --legacy-mem \
> + ./testpmd -n 4 -l 2-4 \
> --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' --
> -i --nb-cores=2 --txd=1024 --rxd=1024
> testpmd>set fwd io
> testpmd>start
>
> 2. Launch virtio-user by below command::
>
> - ./testpmd -n 4 -l 5-6 --socket-mem 1024,1024 \
> - --legacy-mem --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 \
> + ./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_orde
> + r=0,mrg_rxbuf=0,vectorized=1 \
> -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=1 --
> txd=1024 --rxd=1024
> >set fwd mac
> >start
> @@ -186,16 +175,15 @@ Test Case 7: virtio single core performance test
> with vectorized_rx path 1. Bind one port to igb_uio, then launch vhost by
> below command::
>
> rm -rf vhost-net*
> - ./testpmd -n 4 -l 2-4 --socket-mem 1024,1024 --legacy-mem \
> + ./testpmd -n 4 -l 2-4 \
> --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' --
> -i --nb-cores=2 --txd=1024 --rxd=1024
> testpmd>set fwd io
> testpmd>start
>
> 2. Launch virtio-user by below command::
>
> - ./testpmd -n 4 -l 5-6 --socket-mem 1024,1024 \
> - --legacy-mem --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 \
> + ./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_orde
> + r=0,mrg_rxbuf=0,vectorized=1 \
> -- -i --tx-offloads=0x0 --nb-cores=1 --txd=1024 --rxd=1024
> >set fwd mac
> >start
> @@ -208,15 +196,14 @@ Test Case 8: virtio single core performance test
> with virtio 1.1 inorder mergeab 1. Bind one port to igb_uio, then launch
> vhost by below command::
>
> rm -rf vhost-net*
> - ./testpmd -n 4 -l 2-4 --socket-mem 1024,1024 --legacy-mem \
> + ./testpmd -n 4 -l 2-4 \
> --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' --
> -i --nb-cores=2 --txd=1024 --rxd=1024
> testpmd>set fwd io
> testpmd>start
>
> 2. Launch virtio-user by below command::
>
> - ./testpmd -n 4 -l 5-6 --socket-mem 1024,1024 \
> - --legacy-mem --no-pci --file-prefix=virtio \
> + ./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=1,in_order=1 \
> -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=1 --
> txd=1024 --rxd=1024
> >set fwd mac
> @@ -230,16 +217,15 @@ Test Case 9: virtio single core performance test
> with virtio 1.1 inorder non-mer 1. Bind one port to igb_uio, then launch
> vhost by below command::
>
> rm -rf vhost-net*
> - ./testpmd -n 4 -l 2-4 --socket-mem 1024,1024 --legacy-mem \
> + ./testpmd -n 4 -l 2-4 \
> --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' --
> -i --nb-cores=2 --txd=1024 --rxd=1024
> testpmd>set fwd io
> testpmd>start
>
> 2. Launch virtio-user by below command::
>
> - ./testpmd -n 4 -l 5-6 --socket-mem 1024,1024 \
> - --legacy-mem --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,packed_vec=1 \
> + ./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
> >set fwd mac
> >start
> @@ -247,7 +233,7 @@ Test Case 9: virtio single core performance test with
> virtio 1.1 inorder non-mer 3. Send packet with packet generator with
> different packet size, check the throughput.
>
> Test Case 10: virtio single core performance test with virtio 1.1 vectorized
> path -
> ================================================================
> =============
> +===============================================================
> ========
> +==========
>
> 1. Bind one port to igb_uio, then launch vhost by below command::
>
> @@ -260,7 +246,7 @@ Test Case 10: virtio single core performance test with
> virtio 1.1 vectorized pat 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,queues=2,packed_vq=1,mrg_rxbuf=0,in_order=1,packed_vec=1 \
> +
> + --vdev=net_virtio_user0,mac=00:01:02:03:04:05,path=./vhost-net,queues=
> + 2,packed_vq=1,mrg_rxbuf=0,in_order=1,vectorized=1 \
> -- -i --rss-ip --nb-cores=1 --txd=1024 --rxd=1024
> >set fwd mac
> >start
> --
> 2.17.1
prev parent reply other threads:[~2020-04-27 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 21:42 Yinan
2020-04-27 7:51 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC12A99@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).