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 v3] test_plans/pvp_multi_paths_virtio_single_core_performance: add virtio1.1 inorder path test case
Date: Mon, 15 Apr 2019 20:47:25 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA6248F@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190414204008.3850-1-yinan.wang@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yinan
> Sent: Sunday, April 14, 2019 1:40 PM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>
> Subject: [dts] [PATCH v3]
> test_plans/pvp_multi_paths_virtio_single_core_performance: add virtio1.1
> inorder path test case
>
> From: Wang Yinan <yinan.wang@intel.com>
>
> add virtio1.1 inorder path test in
> pvp_multi_paths_virtio_single_core_performance_test_plan.rst
>
> Signed-off-by: Wang Yinan <yinan.wang@intel.com>
> ---
> ...rtio_single_core_performance_test_plan.rst | 80 ++++++++++---------
> 1 file changed, 43 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 5c64d5d..18c192c 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,24 +30,26 @@
> 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 -
> ========================================
> +=========================================================
> +vhost/virtio pvp multi-paths virtio single core test plan
> +=========================================================
>
> Description
> ===========
>
> -Benchmark PVP virtio single core performance with 7 TX/RX PATHs.
> -Includes Mergeable, Normal, Vector_RX, Inorder mergeable, Inorder -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.
> +Benchmark pvp virtio single core performance with 8 tx/rx paths.
> +Includes mergeable, normal, vector_rx, inorder mergeable, inorder
> +no-mergeable, virtio 1.1 mergeable, virtio 1.1 inorder, virtio 1.1 normal
> path.
> +Give 2 cores for vhost and 1 core for virtio, set io fwd at vhost side to lower
> the vhost workload.
>
> -Test Case 1: virtio single core performance test with Virtio 1.1 mergeable
> path -
> ================================================================
> ===============
> +Test flow
> +=========
>
> -flow:
> TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
>
> +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*
> @@ -60,18 +62,15 @@ TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
>
> ./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=1 \
> +
> + --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
> >start
>
> 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
> +Test Case 2: virtio single core performance test with virtio 1.1 normal
> +path
> +===============================================================
> ========
> +=====
>
> 1. Bind one port to igb_uio, then launch vhost by below command::
>
> @@ -85,19 +84,16 @@ TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
>
> ./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 \
> +
> + --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
> >start
>
> 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
> +Test Case 3: virtio single core performance test with inorder mergeable
> +path
>
> ================================================================
> ============
>
> -flow:
> -TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
> -
> 1. Bind one port to igb_uio, then launch vhost by below command::
>
> rm -rf vhost-net*
> @@ -117,12 +113,9 @@ 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
> +Test Case 4: virtio single core performance test with inorder
> +no-mergeable path
>
> ================================================================
> ===============
>
> -flow:
> -TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
> -
> 1. Bind one port to igb_uio, then launch vhost by below command::
>
> rm -rf vhost-net*
> @@ -142,12 +135,9 @@ 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
> +Test Case 5: virtio single core performance test with mergeable path
>
> ================================================================
> ====
>
> -flow:
> -TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
> -
> 1. Bind one port to igb_uio, then launch vhost by below command::
>
> rm -rf vhost-net*
> @@ -167,12 +157,9 @@ 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
> +Test Case 6: virtio single core performance test with normal path
>
> ================================================================
> =
>
> -flow:
> -TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
> -
> 1. Bind one port to igb_uio, then launch vhost by below command::
>
> rm -rf vhost-net*
> @@ -192,12 +179,9 @@ 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
> +Test Case 7: virtio single core performance test with vector_rx path
>
> ================================================================
> ====
>
> -flow:
> -TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
> -
> 1. Bind one port to igb_uio, then launch vhost by below command::
>
> rm -rf vhost-net*
> @@ -216,3 +200,25 @@ TG --> NIC --> Vhost --> Virtio--> Vhost --> NIC --> TG
> >start
>
> 3. Send packet with packet generator with different packet size, check the
> throughput.
> +
> +Test Case 8: virtio single core performance test with virtio 1.1
> +inorder 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>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 \
> + -- -i --tx-offloads=0x0 --enable-hw-vlan-strip --rss-ip --nb-cores=1 --
> txd=1024 --rxd=1024
> + >set fwd mac
> + >start
> +
> +3. Send packet with packet generator with different packet size, check the
> throughput.
> \ No newline at end of file
> --
> 2.17.1
prev parent reply other threads:[~2019-04-15 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 20:40 Yinan
2019-04-15 20:47 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BA6248F@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).