test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "Wang, FeiX Y" <feix.y.wang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wang, FeiX Y" <feix.y.wang@intel.com>
Subject: Re: [dts] [PATCH V1 2/2] add test plan for test suite nsh
Date: Tue, 2 Jan 2018 08:20:44 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62F3CD14@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1513944349-60679-1-git-send-email-feix.y.wang@intel.com>

Fei,
NSH type detect look like one part of unified packet type feature. Could you please check whether this test plan and suite can merged into that suite?

Thanks,
Marvin

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of wang fei
> Sent: Friday, December 22, 2017 8:06 PM
> To: dts@dpdk.org
> Cc: Wang, FeiX Y <feix.y.wang@intel.com>
> Subject: [dts] [PATCH V1 2/2] add test plan for test suite nsh
> 
> Signed-off-by: wang fei <feix.y.wang@intel.com>
> ---
>  test_plans/nsh_test_plan.rst | 97
> ++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 97 insertions(+)
>  create mode 100644 test_plans/nsh_test_plan.rst
> 
> diff --git a/test_plans/nsh_test_plan.rst b/test_plans/nsh_test_plan.rst
> new file mode 100644
> index 0000000..3932313
> --- /dev/null
> +++ b/test_plans/nsh_test_plan.rst
> @@ -0,0 +1,97 @@
> +.. Copyright (c) <2016>, Intel Corporation
> +   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.
> +
> +=========================================
> +Fortville, L2 NSH packet type recognition
> +=========================================
> +
> +Prerequisites
> +=============
> +
> +1. Hardware:
> +   one Fortville NIC (4x 10G or 2x10G or 2x40G or 1x10G)
> +
> +2. software:
> +  dpdk: http://dpdk.org/git/dpdk
> +  scapy: http://www.secdev.org/projects/scapy/
> +
> +3. Assuming that DUT ports ``0`` and ``1`` are connected to the tester's
> port ``A`` and ``B``.
> +
> +Test Case 1: NSH ptype recognition
> +==================================
> +1) start testpmd, start in rxonly mode,
> +
> +./testpmd -c 0xff -n 4 -- -i --portmask=0x3 --txqflags=0
> +testpmd> set fwd rxonly
> +testpmd> set verbose 1
> +testpmd> start
> +
> +2) send packet as the following, verify packet type can be recognized
> correctly.
> +
> +ether+nsh
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x0,NSP=0x000002,NSI=0xff)], iface="ens260f0")
> +
> +ether+nsh+ip
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x1,NSP=0x000002,NSI=0xff)/IP(src="192.168.0.1", dst="192.168.0.2")],
> iface="ens260f0")
> +
> +ether+nsh+ip+icmp
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x1,NSP=0x000002,NSI=0xff)/IP(src="192.168.0.1", dst="192.168.0.2")/ICMP()],
> iface="ens260f0")
> +
> +ether+nsh+ip_frag
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x1,NSP=0x000002,NSI=0xff)/IP(src="192.168.0.1",
> dst="192.168.0.2",frag=1,flags="MF")], iface="ens260f0")
> +
> +ether+nsh+ip+tcp
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x1,NSP=0x000002,NSI=0xff)/IP(src="192.168.0.1",
> dst="192.168.0.2")/TCP(sport=1024,dport=1025)], iface="ens260f0")
> +
> +ether+nsh+ip+udp
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x1,NSP=0x000002,NSI=0xff)/IP(src="192.168.0.1",
> dst="192.168.0.2")/UDP(sport=1024,dport=1025)], iface="ens260f0")
> +
> +ether+nsh+ip+sctp
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x1,NSP=0x000002,NSI=0xff)/IP(src="192.168.0.1",
> dst="192.168.0.2")/SCTP(tag=1)/SCTPChunkData(data='X' * 16)],
> iface="ens260f0")
> +
> +ether+nsh+ipv6
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x2,NSP=0x000002,NSI=0xff)/IPv6(src="2001::1", dst="2003::2")],
> iface="ens260f0")
> +
> +ether+nsh+ipv6+icmp
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x2,NSP=0x000002,NSI=0xff)/IPv6(src="2001::1",
> dst="2003::2",nh=0x3A)/ICMP()], iface="ens260f0")
> +
> +ether+nsh+ipv6_frag
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x2,NSP=0x000002,NSI=0xff)/IPv6(src="2001::1",
> dst="2003::2")/IPv6ExtHdrFragment()], iface="ens260f0")
> +
> +ether+nsh+ipv6+tcp
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x2,NSP=0x000002,NSI=0xff)/IPv6(src="2001::1",
> dst="2003::2")/TCP(sport=1024,dport=1025)], iface="ens260f0")
> +
> +ether+nsh+ipv6+udp
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x2,NSP=0x000002,NSI=0xff)/IPv6(src="2001::1",
> dst="2003::2")/UDP(sport=1024,dport=1025)], iface="ens260f0")
> +
> +ether+nsh+ipv6+sctp
> +sendp([Ether(dst="00:00:00:00:01:00",type=0x894f)/NSH(Len=0x6,NextProto=0
> x2,NSP=0x000002,NSI=0xff)/IPv6(src="2001::1",
> dst="2003::2",nh=0x84)/SCTP(tag=1)/SCTPChunkData(data='X' * 16)],
> iface="ens260f0")
> --
> 2.7.4

      reply	other threads:[~2018-01-02  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 12:05 wang fei
2018-01-02  8:20 ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E62F3CD14@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=feix.y.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).