test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Lin, Xueqin" <xueqin.lin@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Lin, Xueqin" <xueqin.lin@intel.com>
Subject: Re: [dts] [PATCH 1/2] test_plans/generic_flow_api: correct i40e could	support 0x88cc ether type packet
Date: Tue, 6 Aug 2019 08:51:07 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAFD157@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1564999429-118635-1-git-send-email-xueqin.lin@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Lin Xueqin
> Sent: Monday, August 5, 2019 6:04 PM
> To: dts@dpdk.org
> Cc: Lin, Xueqin <xueqin.lin@intel.com>
> Subject: [dts] [PATCH 1/2] test_plans/generic_flow_api: correct i40e could
> support 0x88cc ether type packet
> 
> From: Xueqin Lin <xueqin.lin@intel.com>
> 
> Signed-off-by: Xueqin Lin <xueqin.lin@intel.com>
> 
> ---
>  test_plans/generic_flow_api_test_plan.rst | 10 ++++------
>  1 file changed, 4 insertions(+), 6 deletions(-)
> 
> diff --git a/test_plans/generic_flow_api_test_plan.rst
> b/test_plans/generic_flow_api_test_plan.rst
> index f53e7c7..380d9e8 100644
> --- a/test_plans/generic_flow_api_test_plan.rst
> +++ b/test_plans/generic_flow_api_test_plan.rst
> @@ -70,26 +70,24 @@ Test case: Fortville ethertype
>      testpmd> flow validate 0 ingress pattern eth type is 0x88cc / end actions
> queue index 5 / end
>      testpmd> flow create 0 ingress pattern eth type is 0x88cc / end actions
> queue index 6 / end
> 
> -   the i40e don't support the 0x88cc eth type packet. so the last two
> commands
> -   failed.
> -
>  3. send packets::
> 
>      pkt1 = Ether(dst="ff:ff:ff:ff:ff:ff")/ARP(pdst="192.168.1.1")
>      pkt2 = Ether(dst="00:11:22:33:44:55", type=0x88BB)/Raw('x' * 20)
>      pkt3 = Ether(dst="00:11:22:33:44:55", type=0x88e5)/Raw('x' * 20)
>      pkt4 = Ether(dst="00:11:22:33:44:55", type=0x8864)/Raw('x' * 20)
> +    pkt5 = Ether(dst="00:11:22:33:44:55", type=0x88cc)/Raw('x' * 20)
> 
> -   verify pkt1 to queue 2, and pkt2 to queue 3, pkt3 to queue 4, pkt4
> dropped.
> +   verify pkt1 to queue 2, and pkt2 to queue 3, pkt3 to queue 4, pkt4
> dropped, pkt5 to queue 6.
> 
>  4. verify rules can be listed and destroyed::
> 
>      testpmd> flow list 0
>      testpmd> flow destroy 0 rule 0
> -    verify pkt1 to queue 0, and pkt2 to queue 3, pkt3 to queue 4,
> +    verify pkt1 to queue 0, and pkt2 to queue 3, pkt3 to queue 4, pkt4
> dropped, pkt5 to queue 6.
>      testpmd> flow list 0
>      testpmd> flow flush 0
> -    verify pkt1 to queue 0, and pkt2 to queue 0, pkt3 to queue 0, pkt4 to
> queue 0.
> +    verify pkt1 to queue 0, and pkt2 to queue 0, pkt3 to queue 0, pkt4 to
> queue 0, pkt5 to queue 0.
>      testpmd> flow list 0
> 
> 
> --
> 2.7.5


      reply	other threads:[~2019-08-06  8:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 10:03 Lin Xueqin
2019-08-06  8: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=8CE3E05A3F976642AAB0F4675D0AD20E0BAFD157@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=xueqin.lin@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).