From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Peng, Yuan" <yuan.peng@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>
Subject: Re: [dts] [PATCH] test_plans: Add a case to vxlan_test_plan.rst
Date: Wed, 3 Jul 2019 05:52:35 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAD9283@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1561975967-117447-1-git-send-email-yuan.peng@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Peng Yuan
> Sent: Monday, July 1, 2019 6:13 PM
> To: dts@dpdk.org
> Cc: Peng, Yuan <yuan.peng@intel.com>
> Subject: [dts] [PATCH] test_plans: Add a case to vxlan_test_plan.rst
>
> Add a case to vxlan_test_plan.rst
>
> Signed-off-by: Peng Yuan <yuan.peng@intel.com>
>
> diff --git a/test_plans/vxlan_test_plan.rst b/test_plans/vxlan_test_plan.rst
> index 83c99ac..60cfec9 100644
> --- a/test_plans/vxlan_test_plan.rst
> +++ b/test_plans/vxlan_test_plan.rst
> @@ -33,7 +33,6 @@
> =====================
> Fortville Vxlan Tests
> =====================
> -
> Cloud providers build virtual network overlays over existing network
> infrastructure that provide tenant isolation and scaling. Tunneling layers
> added to the packets carry the virtual networking frames over @@ -58,7
> +57,7 @@ Test Case: Vxlan ipv4 packet detect
> ===================================
> Start testpmd with tunneling packet type to vxlan::
>
> - testpmd -c ffff -n 4 -- -i --rxq=4 --txq=4 --nb-cores=8 --nb-ports=2 --tx-
> offloads=0x8fff
> + testpmd -c ffff -n 4 -- -i --rxq=4 --txq=4 --nb-cores=8
> + --nb-ports=2
>
> Set rxonly packet forwarding mode and enable verbose log::
>
> @@ -85,13 +84,11 @@ Send packet as table listed and check dumped packet
> type the same as column
> | Yes | Ipv4 | Vxlan | Yes | Ipv4 | Udp |
> PKT_RX_IPV4_HDR_EXT | None |
> +------------+----------+-----------+------------+----------+-----------+---------------------+------
> -----+
>
> -
> -
> Test Case: Vxlan ipv6 packet detect
> ===================================
> Start testpmd with tunneling packet type to vxlan::
>
> - testpmd -c ffff -n 4 -- -i --disable-rss --rxq=4 --txq=4 --nb-cores=8 --nb-
> ports=2 --tx-offloads=0x8fff
> + testpmd -c ffff -n 4 -- -i --disable-rss --rxq=4 --txq=4
> + --nb-cores=8 --nb-ports=2
>
> Set rxonly packet forwarding mode and enable verbose log::
>
> @@ -118,13 +115,11 @@ column "Rx packet type".
> | Yes | Ipv6 | Vxlan | Yes | Ipv6 | Udp |
> PKT_RX_IPV6_HDR_EXT | None |
> +------------+----------+-----------+------------+----------+-----------+---------------------+------
> -----+
>
> -
> Test Case: Vxlan ipv4 checksum offload
> ======================================
> -
> Start testpmd with tunneling packet type to vxlan::
>
> - testpmd -c ffff -n 4 -- -i --rxq=4 --txq=4 --nb-cores=8 --nb-ports=2 --tx-
> offloads=0x8fff
> + testpmd -c ffff -n 4 -- -i --rxq=4 --txq=4 --nb-cores=8
> + --nb-ports=2
>
> Set csum packet forwarding mode and enable verbose log::
>
> @@ -216,7 +211,6 @@ checksum corrected and there's correct l4 chksum
> error counter increased.
> | Yes | Ipv4 | Vxlan | None | Ipv4 | Bad Sctp |
> +------------+----------+-----------+------------+----------+-----------+
>
> -
> Test Case: Vxlan ipv6 checksum offload
> ======================================
> Start testpmd with tunneling packet type::
> @@ -285,12 +279,12 @@ increased.
> | Yes | Ipv6 | Vxlan | Yes | Ipv4 | Bad Sctp |
> +------------+----------+-----------+------------+----------+-----------+
>
> -Test Case: Cloud Filter
> +Test Case: Tunnel Filter
> ========================
> Start testpmd with tunneling packet type to vxlan and disable receive side
> scale for hardware limitation::
>
> - testpmd -c ffff -n 4 -- -i --disable-rss --rxq=4 --txq=4 --nb-cores=8 --nb-
> ports=2 --tx-offloads=0x8fff
> + testpmd -c ffff -n 4 -- -i --disable-rss --rxq=4 --txq=4
> + --nb-cores=8 --nb-ports=2
>
> Set rxonly packet forwarding mode and enable verbose log::
>
> @@ -319,12 +313,18 @@ Then send one packet and check packet was
> forwarded into right queue.
> | No | No | No | No | Yes | No | 1 |
> +------------+------------+------------+----------+----------+--------+-------+
>
> -
> Add Cloud filter to max number will be failed.
>
> Remove Cloud filter which has been added. Then send one packet and check
> packet was received in queue 0.
>
> +Test Case: Tunnel Filter invalid
> +================================
> +Start testpmd with tunneling packet type to vxlan and disable receive
> +side scale for hardware limitation::
> +
> + testpmd -c ffff -n 4 -- -i --disable-rss --rxq=4 --txq=4
> + --nb-cores=8 --nb-ports=2
> +
> Add Cloud filter with invalid Mac address "00:00:00:00:01" will be failed.
>
> Add Cloud filter with invalid ip address "192.168.1.256" will be failed.
> @@ -337,7 +337,6 @@ Add Cloud filter with invalid queue id "64" will be
> failed.
>
> Test Case: Vxlan Checksum Offload Performance Benchmarking
> ==========================================================
> -
> The throughput is measured for each of these cases for vxlan tx checksum
> offload of "all by software", "L3 offload by hardware", "L4 offload by
> hardware", "l3&l4 offload by hardware".
> --
> 2.14.3
prev parent reply other threads:[~2019-07-03 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 10:12 Peng Yuan
2019-07-03 5:52 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BAD9283@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yuan.peng@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).