test suite reviews and discussions
 help / color / mirror / Atom feed
From: <usurekha@marvell.com>
To: <dts@dpdk.org>
Cc: <pvukkisala@marvell.com>, <zzhou@marvell.com>,
	usurekha <usurekha@marvell.com>
Subject: [dts] [PATCH] tests/TestSuite_rxtx_offload.py:Added cavium_nic and tcp/udp l4 csum verification command for cavium
Date: Thu, 26 Nov 2020 16:32:59 +0530	[thread overview]
Message-ID: <1606388579-6077-1-git-send-email-usurekha@marvell.com> (raw)

From: usurekha <usurekha@marvell.com>

Signed-off-by: usurekha <usurekha@marvell.com>
---
 tests/TestSuite_rxtx_offload.py | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/tests/TestSuite_rxtx_offload.py b/tests/TestSuite_rxtx_offload.py
index bf2c901..9257174 100644
--- a/tests/TestSuite_rxtx_offload.py
+++ b/tests/TestSuite_rxtx_offload.py
@@ -90,7 +90,7 @@ class TestRxTx_Offload(TestCase):
         # Support i40e/ixgbe NICs
         self.verify(self.nic in ["fortville_eagle", "fortville_spirit","fortville_25g",
                                  "fortville_spirit_single", "fortpark_TLV","fortpark_BASE-T", "carlsville",
-                                 "niantic", "twinpond", "sagepond", "sageville", "foxville"], "NIC Unsupported: " + str(self.nic))
+                                 "niantic", "twinpond", "sagepond", "sageville", "foxville", "cavium_a063", "cavium_a064"], "NIC Unsupported: " + str(self.nic))
         # Based on h/w type, choose how many ports to use
         self.dut_ports = self.dut.get_ports(self.nic)
         # Verify that enough ports are available
@@ -271,7 +271,10 @@ class TestRxTx_Offload(TestCase):
                     else:
                         self.verify("PKT_RX_IP_CKSUM_GOOD" in line, "ipv4 checksum flag is wrong!")
                     if ("udp" in flags) or ("tcp" in flags):
-                        self.verify("PKT_RX_L4_CKSUM_BAD" in line, "L4 checksum flag is wrong!")
+                        if self.nic in ['cavium_a063', 'cavium_a064']:
+                            self.verify("PKT_RX_L4_CKSUM_BAD" or "PKT_RX_L4_CKSUM_UNKNOWN" in line, "L4 checksum flag is wrong!")
+                        else:
+                            self.verify("PKT_RX_L4_CKSUM_BAD" in line, "L4 checksum flag is wrong!")
                     else:
                         self.verify(("PKT_RX_L4_CKSUM_GOOD" in line) or ("PKT_RX_L4_CKSUM_UNKNOWN" in line), "L4 checksum flag is wrong!")
         # collect the tx checksum result
@@ -431,7 +434,7 @@ class TestRxTx_Offload(TestCase):
         self.pmdout.start_testpmd("%s" % self.cores, "--rxq=4 --txq=4")
         capabilities = self.check_port_capability("rx")
         for capability in capabilities:
-            if self.nic == 'foxville' and capability == 'sctp_cksum':
+            if self.nic in ['foxville', 'cavium_a063', 'cavium_a064']  and capability == 'sctp_cksum':
                 continue
             if capability != "jumboframe":
                 self.dut.send_expect("port stop 0", "testpmd> ")
@@ -505,7 +508,7 @@ class TestRxTx_Offload(TestCase):
         self.dut.send_expect("set fwd txonly", "testpmd> ")
         self.dut.send_expect("set verbose 1", "testpmd> ")
         if (self.nic in ["fortville_eagle", "fortville_spirit","fortville_25g",
-                         "fortville_spirit_single", "fortpark_TLV","fortpark_BASE-T", "carlsville"]):
+                         "fortville_spirit_single", "fortpark_TLV","fortpark_BASE-T", "carlsville","cavium_a063", "cavium_a064"]):
             self.dut.send_expect("port stop 0", "testpmd> ")
             self.dut.send_expect("port config 0 tx_offload mbuf_fast_free off", "testpmd> ")
         self.check_port_config("tx", "NULL")
-- 
2.7.4


             reply	other threads:[~2020-11-26 11:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 11:02 usurekha [this message]
2020-12-01  8:45 ` 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=1606388579-6077-1-git-send-email-usurekha@marvell.com \
    --to=usurekha@marvell.com \
    --cc=dts@dpdk.org \
    --cc=pvukkisala@marvell.com \
    --cc=zzhou@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).