test suite reviews and discussions
 help / color / mirror / Atom feed
From: Qin Sun <qinx.sun@intel.com>
To: dts@dpdk.org
Cc: Qin Sun <qinx.sun@intel.com>
Subject: [dts] [PATCH V1 1/2] tests/cvl_limit_value_test: modify maximum value of switch rule
Date: Thu, 29 Jul 2021 13:49:35 +0000	[thread overview]
Message-ID: <20210729134935.4514-1-qinx.sun@intel.com> (raw)

confirm with developer that CVL support up to 32K FLU entries.Firmware allocates some
default entries first, the actual entries can't be calculated and depend on hardware.
there is no formula to figure out the specific rule numbers of different environment
configurations,so can't acquire the actual number of free entries.
dts case needs to modify the maximum value of switch rule to a proper value


Signed-off-by: Qin Sun <qinx.sun@intel.com>
---
 tests/TestSuite_cvl_limit_value_test.py | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/tests/TestSuite_cvl_limit_value_test.py b/tests/TestSuite_cvl_limit_value_test.py
index 2d0ad412..f8224258 100644
--- a/tests/TestSuite_cvl_limit_value_test.py
+++ b/tests/TestSuite_cvl_limit_value_test.py
@@ -48,7 +48,7 @@ tv_max_rule_number = {
     "matched": {"scapy_str": [],
                 "check_func": {"func": rfc.check_vf_rx_packets_number,
                                "param": {"expect_port": 1}},
-                "expect_results": {"expect_pkts": 32563}},
+                "expect_results": {"expect_pkts": 32500}},
     "mismatched": {
         "scapy_str": ['Ether(dst="68:05:ca:8d:ed:a8")/IP(src="192.167.0.1")/TCP(sport=25,dport=23)/("X"*480)'],
         "check_func": {"func": rfc.check_vf_rx_packets_number,
@@ -908,13 +908,13 @@ class TestCvlLimitValue(TestCase):
 
         # set up 4 vfs on 1 pf environment
         self.setup_1pf_vfs_env()
-        # create 32563 rules with the same pattern, but different input set to file
+        # create 32500 rules with the same pattern, but different input set to file
         src_file = 'dep/testpmd_cmds_32k_switch_rules'
         flows = open(src_file, mode='w')
         rule_count = 1
         for i in range(0, 255):
             for j in range(0, 255):
-                if not rule_count > 32563:
+                if not rule_count > 32500:
                     flows.write(
                         'flow create 0 ingress pattern eth / ipv4 src is 192.168.%d.%d / end actions vf id 1 / end \n' % (
                         i, j))
@@ -924,12 +924,12 @@ class TestCvlLimitValue(TestCase):
                     rule_count += 1
                 else:
                     break
-            if rule_count > 32563:
+            if rule_count > 32500:
                 break
         flows.close()
         dut_file_dir = '/tmp/'
         self.dut.session.copy_file_to(src_file, dut_file_dir)
-        # launch testpmd with 32563 rules
+        # launch testpmd with 32500 rules
         vf0_pci = self.sriov_vfs_port_0[0].pci
         vf1_pci = self.sriov_vfs_port_0[1].pci
         all_eal_param = self.dut.create_eal_parameters(cores="1S/4C/1T", ports=[vf0_pci, vf1_pci],
@@ -939,8 +939,8 @@ class TestCvlLimitValue(TestCase):
         self.testpmd_status = "running"
         self.dut.send_expect("set portlist 1", "testpmd> ", 15)
         self.dut.send_expect("set fwd rxonly", "testpmd> ", 15)
-        # check the rule list with 32563 rules
-        rule_list_num = list(range(0, 32563))
+        # check the rule list with 32500 rules
+        rule_list_num = list(range(0, 32500))
         rule_list = [str(x) for x in rule_list_num]
         self.check_switch_filter_rule_list(0, rule_list)
         # create other rules to make switch filter table full
-- 
2.17.1


             reply	other threads:[~2021-07-29  5:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29 13:49 Qin Sun [this message]
2021-07-29  5:27 ` Sun, QinX
2021-08-10  7:01   ` 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=20210729134935.4514-1-qinx.sun@intel.com \
    --to=qinx.sun@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).