From: sunqin <qinx.sun@intel.com>
To: dts@dpdk.org
Cc: sunqin <qinx.sun@intel.com>
Subject: [dts] [PATCH V1] tests/cvl_advanced_rss_gtpu: remove destroy rule step
Date: Thu, 4 Feb 2021 11:35:47 +0000 [thread overview]
Message-ID: <20210204113547.3889-1-qinx.sun@intel.com> (raw)
The action after deleting rule is not guaranteed, so remove related steps.
Signed-off-by: sunqin <qinx.sun@intel.com>
---
| 12 ------------
1 file changed, 12 deletions(-)
--git a/tests/TestSuite_cvl_advanced_rss_gtpu.py b/tests/TestSuite_cvl_advanced_rss_gtpu.py
index b41a5d4a..8dd9fdbc 100755
--- a/tests/TestSuite_cvl_advanced_rss_gtpu.py
+++ b/tests/TestSuite_cvl_advanced_rss_gtpu.py
@@ -4863,18 +4863,6 @@ class TestCVLAdvancedRSSGTPU(TestCase):
self.verify(hash_values[4] != hash_values[3], 'packet 5 should has different hash value with packet 4')
self.verify(hash_values[5] == hash_values[3], 'packet 6 should has same hash value with packet 4')
- self.rssprocess.destroy_rule(port_id=0, rule_id=rule0)
- hash_values, queues = self.rssprocess.send_pkt_get_hash_queues(pkts1[3:])
- self.verify(hash_values[1] != hash_values[0], 'should get different hash values')
- self.verify(hash_values[2] == hash_values[0], 'should get same hash values')
-
- rule2 = self.rssprocess.create_rule(rules[0])
- hash_values, queues = self.rssprocess.send_pkt_get_hash_queues(pkts1)
- self.verify(hash_values[1] == hash_values[0], 'packet 2 should has same hash value with packet 1')
- self.verify(hash_values[2] != hash_values[0], 'packet 3 should has different hash value with packet 1')
- self.verify(hash_values[4] == hash_values[3], 'packet 5 should has same hash value with packet 4')
- self.verify(hash_values[5] != hash_values[3], 'packet 6 should has different hash value with packet 4')
-
def test_ipv4_gtpu_eh_ipv4_and_ipv4_gtpu_eh_ipv4_udp_tcp(self):
self.switch_testpmd(enable_rss=True)
pkts1 = [
--
2.17.1
next reply other threads:[~2021-02-04 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 11:35 sunqin [this message]
2021-02-04 3:10 ` Sun, QinX
2021-02-19 7:42 ` 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=20210204113547.3889-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).