test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhu, WenhuiX" <wenhuix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, WenhuiX" <wenhuix.zhu@intel.com>
Subject: Re: [dts] [PATCH V2] tests/queue_region:change fortpark flowtype
Date: Wed, 7 Aug 2019 03:41:21 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAFEC82@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1563242137-119117-1-git-send-email-wenhuix.zhu@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhuwenhui
> Sent: Tuesday, July 16, 2019 9:56 AM
> To: dts@dpdk.org
> Cc: Zhu, WenhuiX <wenhuix.zhu@intel.com>
> Subject: [dts] [PATCH V2] tests/queue_region:change fortpark flowtype
> 
> if nic is x722,ipv6-udp belongs to flowtype 39
> 
> Signed-off-by: zhuwenhui <wenhuix.zhu@intel.com>
> ---
>  tests/TestSuite_queue_region.py | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/TestSuite_queue_region.py
> b/tests/TestSuite_queue_region.py index 01842c2..28e7a58 100644
> --- a/tests/TestSuite_queue_region.py
> +++ b/tests/TestSuite_queue_region.py
> @@ -212,7 +212,10 @@ class TestQueue_region(TestCase):
>          self.dut.send_expect("set port 0 queue-region region_id 2 flowtype 33",
> "testpmd> ")
>          self.dut.send_expect("set port 0 queue-region region_id 4 flowtype 35",
> "testpmd> ")
>          self.dut.send_expect("set port 0 queue-region region_id 6 flowtype 36",
> "testpmd> ")
> -        self.dut.send_expect("set port 0 queue-region region_id 2 flowtype 41",
> "testpmd> ")
> +        if self.nic in ["fortpark_TLV"]:
> +            self.dut.send_expect("set port 0 queue-region region_id 2 flowtype
> 39", "testpmd> ")
> +        else:
> +            self.dut.send_expect("set port 0 queue-region region_id 2
> + flowtype 41", "testpmd> ")
>          self.dut.send_expect("set port 0 queue-region region_id 3 flowtype 43",
> "testpmd> ")
>          self.dut.send_expect("set port 0 queue-region region_id 4 flowtype 44",
> "testpmd> ")
>          self.dut.send_expect("set port 0 queue-region region_id 5 flowtype 45",
> "testpmd> ") @@ -223,7 +226,7 @@ class TestQueue_region(TestCase):
>          # region  |  queue       |  flowtype  |  packet_type
>          #   0     |  1           |  31        |  IPv4_UDP
>          #   1     |  3,4         |  32        |  IPv4_TCP_SYN
> -        #   2     |  6,7         |  33,41     |  IPv4_TCP, IPv6_UDP
> +        #   2     |  6,7         |  33,41/39  |  IPv4_TCP, IPv6_UDP
>          #   3     |  8,9         |  43        |  IPv6_TCP
>          #   4     |  11,12,13,14 |  35,44     |  IPv4_Other, IPv6_SCTP
>          #   5     |  15          |  45        |  IPv6_Other
> --
> 2.17.2


      parent reply	other threads:[~2019-08-07  3:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16  1:55 zhuwenhui
2019-07-16  1:53 ` Zhu, ShuaiX
2019-08-07  3:41 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BAFEC82@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=wenhuix.zhu@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).