test suite reviews and discussions
 help / color / mirror / Atom feed
From: Xueqin Lin <xueqin.lin@intel.com>
To: dts@dpdk.org
Cc: Xueqin Lin <xueqin.lin@intel.com>
Subject: [dts] [PATCH 2/3] tests/shutdown_api: add rx/tx descriptor status test for intel nics
Date: Tue, 28 Apr 2020 00:17:06 -0400	[thread overview]
Message-ID: <1588047426-91326-1-git-send-email-xueqin.lin@intel.com> (raw)

rx/tx descriptor status case could support igb, ixgbe, i40e nics

Signed-off-by: Xueqin Lin <xueqin.lin@intel.com>

---
 tests/TestSuite_shutdown_api.py | 22 +++++++++++++++-------
 1 file changed, 15 insertions(+), 7 deletions(-)

diff --git a/tests/TestSuite_shutdown_api.py b/tests/TestSuite_shutdown_api.py
index 181a385..b29ae9b 100644
--- a/tests/TestSuite_shutdown_api.py
+++ b/tests/TestSuite_shutdown_api.py
@@ -787,22 +787,30 @@ class TestShutdownApi(TestCase):
     def test_check_rxtx_desc_status(self):
         """
         Check tx and rx descriptors status.
+        When rx_descriptor_status is used, status can be “AVAILABLE”, “DONE” or “UNAVAILABLE”.
+        When tx_descriptor_status is used, status can be “FULL”, “DONE” or “UNAVAILABLE.”
         """
-        self.pmdout.start_testpmd("Default", "--portmask=%s --port-topology=loop" % utils.create_mask(self.ports), socket=self.ports_socket)
+        self.pmdout.start_testpmd("Default", "--portmask=%s --port-topology=loop --txq=16 --rxq=16 --txd=4096 --rxd=4096" % utils.create_mask(self.ports), socket=self.ports_socket)
 
         for i in range(3):
+            rxqid = randint(0, 16)
             self.desc = randint(0, 4095)
-            out = self.dut.send_expect("show port %s rxq 0 desc %s status" % (self.ports[0], self.desc), "testpmd> ")
+            out = self.dut.send_expect("show port %s rxq %s desc %s status" % (self.ports[0], rxqid, self.desc), "testpmd> ")
             self.verify(
-               "Desc status = AVAILABLE" in out, "RX descriptor status is improper")
+                "Desc status = AVAILABLE" in out or "Desc status = DONE" in out or "Desc status = UNAVAILABLE" in out,
+                "RX descriptor status is improper")
             self.verify(
-               "Bad arguments" not in out, "RX descriptor status is not supported")
+                "Bad arguments" not in out and "Invalid queueid" not in out,
+                "RX descriptor status is not supported")
+            txqid = randint(0, 16)
             self.desc = randint(0, 511)
-            out = self.dut.send_expect("show port %s txq 0 desc %s status" % (self.ports[0], self.desc), "testpmd> ")
+            out = self.dut.send_expect("show port %s txq %s desc %s status" % (self.ports[0], txqid, self.desc), "testpmd> ")
             self.verify(
-               "Desc status = FULL" in out, "TX descriptor status is improper")
+                "Desc status = FULL" in out or "Desc status = DONE" in out or "Desc status = UNAVAILABLE" in out,
+                "TX descriptor status is improper")
             self.verify(
-               "Bad arguments" not in out, "TX descriptor status is not supported")
+                "Bad arguments" not in out and "Invalid queueid" not in out,
+                "TX descriptor status is not supported")
 
     def tear_down(self):
         """
-- 
2.7.5


                 reply	other threads:[~2020-04-28 10:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1588047426-91326-1-git-send-email-xueqin.lin@intel.com \
    --to=xueqin.lin@intel.com \
    --cc=dts@dpdk.org \
    /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).