test suite reviews and discussions
 help / color / mirror / Atom feed
From: <nareddy@marvell.com>
To: <dts@dpdk.org>
Cc: <fmasood@marvell.com>, <avijay@marvell.com>,
	Praneeth Reddy <nareddy@marvell.com>
Subject: [dts] [PATCH] TestSuite_nvgre.py: Modified packet type for cavium_a064
Date: Mon, 12 Aug 2019 10:40:35 +0530	[thread overview]
Message-ID: <1565586635-833-1-git-send-email-nareddy@marvell.com> (raw)

From: Praneeth Reddy <nareddy@marvell.com>

For cavium_a064 packet type is L3_IPV4/L3_IPV6

Signed-off-by: Praneeth Reddy <nareddy@marvell.com>
---
 tests/TestSuite_nvgre.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/TestSuite_nvgre.py b/tests/TestSuite_nvgre.py
index aea915c..62aac3a 100644
--- a/tests/TestSuite_nvgre.py
+++ b/tests/TestSuite_nvgre.py
@@ -162,7 +162,7 @@ class NvgreTestConfig(object):
         """
         Return nvgre packet type
         """
-        if "cavium_a063" in nic:
+        if (self.nic in ["cavium_a063", "cavium_a064"]):
             if self.outer_ip_proto !=47:
                 if self.outer_l3_type == 'IPv4':
                     return 'L3_IPV4'
@@ -361,7 +361,7 @@ class TestNvgre(TestCase):
         nvgre Prerequisites
         """
         # this feature only enable in FVL now
-        if self.nic in ["fortville_eagle", "fortville_spirit", "fortville_spirit_single", "fortville_25g", "fortpark_TLV", "cavium_a063"]:
+        if self.nic in ["fortville_eagle", "fortville_spirit", "fortville_spirit_single", "fortville_25g", "fortpark_TLV", "cavium_a063", "cavium_a064"]:
             self.compile_switch = 'CONFIG_RTE_LIBRTE_I40E_INC_VECTOR'
         elif self.nic in ["sageville", "sagepond"]:
             self.compile_switch = 'CONFIG_RTE_IXGBE_INC_VECTOR'
-- 
1.8.3.1


             reply	other threads:[~2019-08-12  5:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12  5:10 nareddy [this message]
2019-08-12  7:04 ` Tu, Lijuan

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=1565586635-833-1-git-send-email-nareddy@marvell.com \
    --to=nareddy@marvell.com \
    --cc=avijay@marvell.com \
    --cc=dts@dpdk.org \
    --cc=fmasood@marvell.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).