From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Ma, LihongX" <lihongx.ma@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhang, Yuwei1" <yuwei1.zhang@intel.com>,
"Ma, LihongX" <lihongx.ma@intel.com>
Subject: Re: [dts] [PATCH V1] add testplan of vxlan gpe support in i40e
Date: Tue, 23 Apr 2019 19:29:54 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA65745@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1555959599-383-1-git-send-email-lihongx.ma@intel.com>
Could you please and hardware requirements in your test plan?
From your file name, I guess it only support 700 series NIC.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Monday, April 22, 2019 12:00 PM
> To: dts@dpdk.org
> Cc: Zhang, Yuwei1 <yuwei1.zhang@intel.com>; Ma, LihongX
> <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V1] add testplan of vxlan gpe support in i40e
>
> Signed-off-by: lihong <lihongx.ma@intel.com>
> ---
> test_plans/vxlan_gpe_support_in_i40e.rst | 105
> +++++++++++++++++++++++++++++++
> 1 file changed, 105 insertions(+)
> create mode 100644 test_plans/vxlan_gpe_support_in_i40e.rst
>
> diff --git a/test_plans/vxlan_gpe_support_in_i40e.rst
> b/test_plans/vxlan_gpe_support_in_i40e.rst
> new file mode 100644
> index 0000000..ababe32
> --- /dev/null
> +++ b/test_plans/vxlan_gpe_support_in_i40e.rst
> @@ -0,0 +1,105 @@
> +.. Copyright (c) <2016-2019> Intel Corporation
[Lijuan] 2016-2019 should be 2019
> + All rights reserved.
> +
> + Redistribution and use in source and binary forms, with or without
> + modification, are permitted provided that the following conditions
> + are met:
> +
> + - Redistributions of source code must retain the above copyright
> + notice, this list of conditions and the following disclaimer.
> +
> + - Redistributions in binary form must reproduce the above copyright
> + notice, this list of conditions and the following disclaimer in
> + the documentation and/or other materials provided with the
> + distribution.
> +
> + - Neither the name of Intel Corporation nor the names of its
> + contributors may be used to endorse or promote products derived
> + from this software without specific prior written permission.
> +
> + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
> CONTRIBUTORS
> + "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
> NOT
> + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
> FITNESS
> + FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
> + COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
> INDIRECT,
> + INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> + (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
> GOODS OR
> + SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> + HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
> CONTRACT,
> + STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> + ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
> ADVISED
> + OF THE POSSIBILITY OF SUCH DAMAGE.
> +
> +============================
> +I40E VXLAN-GPE Support Tests
> +============================
> +
> +Test Case 1: VXLAN-GPE ipv4 packet detect
> +=========================================
> +1. Start testpmd::
> +
> + # testpmd -c 0xf -n 4 -- -i
> +
> +2. Add VXLAN-GPE packet type support in test pmd and enable verbose log::
> +
> + testpmd> set fwd io
> + testpmd> set verbose 1
> + testpmd> port config 0 udp_tunnel_port add vxlan-gpe 4790
> +
> +3. Send VXLAN-GPE packets to testpmd and check received packets::
> +
> + scapy>
> pkt=Ether(dst="3C:FD:FE:A8:C8:20")/IP(src="18.0.0.1")/UDP(dport=4790,sport
> =43)/VXLAN(flags=12)/IP(src="10.0.0.1")
> + scapy> sendp(pkt1, iface="ens802f1", count=1)
> +
> +4. Expected output from testpmd::
> +
> + src=00:00:00:00:00:00 - dst=3C:FD:FE:A8:C8:20 - type=0x0800 - length=70 -
> nb_segs=1 - RSS hash=0x51ed6fc5 - RSS
> + queue=0x2 - hw ptype: L2_ETHER L3_IPV4_EXT_UNKNOWN
> TUNNEL_GRENAT INNER_L3_IPV4_EXT_UNKNOWN
> + INNER_L4_NONFRAG - sw ptype: L2_ETHER L3_IPV4 L4_UDP - l2_len=14 -
> l3_len=20 - l4_len=8
> + - VXLAN packet: packet type =24721, Destination UDP port =4790, VNI
> + = 0 - Receive queue=0x2
> +
> +Test Case 2: VXLAN-GPE tunnel remove test
> +=========================================
> +1. After Test Case 1, delete the VXLAN-GPE packet type::
> +
> + testpmd> port config 0 udp_tunnel_port rm vxlan-gpe 4790
> +
> +2. Send VXLAN-GPE packets to testpmd and check the received packets
> +
> +3. Expected result::
> +
> + testpmd should treat the packet as a normal UDP packet
> +
> +Test Case 3: Tunnel filter VXLAN-GPE support
> +============================================
> +1. 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
> +
> +2. Set rxonly packet forwarding mode and enable verbose log::
> +
> + testpmd> set fwd rxonly
> + testpmd> set verbose 1
> +
> +3. Add one new Cloud filter as table listed first::
> +
> + testpmd> tunnel_filter add 0 11:22:33:44:55:66 00:00:20:00:00:01
> + 192.168.2.2 1 vxlan-gpe imac-ivlan 1 3
> +
> +4. Then send one packet and check packet was forwarded into right queue.
> +
> ++------------+------------+------------+----------+----------+--------+-------+
> +| Outer Mac | Inner Mac | Inner Vlan | Outer Ip | Inner Ip | Vni ID |
> +| Queue |
> ++------------+------------+------------+----------+----------+--------+-------+
> +| No | Yes | Yes | No | No | No | 1 |
> ++------------+------------+------------+----------+----------+--------+-------+
> +| No | Yes | Yes | No | No | Yes | 1 |
> ++------------+------------+------------+----------+----------+--------+-------+
> +| No | Yes | No | No | No | Yes | 1 |
> ++------------+------------+------------+----------+----------+--------+-------+
> +| No | Yes | No | No | No | No | 1 |
> ++------------+------------+------------+----------+----------+--------+-------+
> +| Yes | Yes | No | No | Yes | Yes | 1 |
> ++------------+------------+------------+----------+----------+--------+-------+
> +| No | No | No | No | Yes | No | 1 |
> ++------------+------------+------------+----------+----------+--------+-------+
> --
> 2.7.4
prev parent reply other threads:[~2019-04-23 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 18:59 lihong
2019-04-23 2:22 ` Zhang, Yuwei1
2019-04-23 19:29 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BA65745@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@intel.com \
--cc=yuwei1.zhang@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).