From: qifu <qi.fu@intel.com>
To: dts@dpdk.org
Cc: qifu <qi.fu@intel.com>
Subject: [dts] [PATCH V1]test_plans/cvl_advanced_iavf_rss_gtpu_test_plan:remove steps of destroy rss rules for gtpu cases
Date: Thu, 28 Jan 2021 10:55:39 -0500 [thread overview]
Message-ID: <20210128155539.27471-1-qi.fu@intel.com> (raw)
synced with developer, the behavior after destroy rss rules are not unified.
so delete the steps after destroying rss rules.
Signed-off-by: qifu <qi.fu@intel.com>
---
| 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
--git a/test_plans/cvl_advanced_iavf_rss_gtpu_test_plan.rst b/test_plans/cvl_advanced_iavf_rss_gtpu_test_plan.rst
index 0b5cfc59..fd2e62c9 100644
--- a/test_plans/cvl_advanced_iavf_rss_gtpu_test_plan.rst
+++ b/test_plans/cvl_advanced_iavf_rss_gtpu_test_plan.rst
@@ -253,9 +253,7 @@ run the same test steps as below:
check all the packets are distributed to queues by rss.
note: if there is not this type packet in the case, omit this step.
-7. distroy the rule and list rule.
-8. send same packets with step 3.
- check the received packet has different hash value with which in step 3(including the case has no hash value).
+7. destroy the rule and list rule. check the flow list has no rule.
================================
@@ -2920,7 +2918,7 @@ all the test cases run the same test steps as below:
check the received packets have same hash value.
check both the packets are distributed to queues by rss.
5. destroy the rule and list rule.
-6. send the packet in step 3.
+6. send the packet in step 4.
check the received packet has different hash value with which in step 3(including the case has no hash value).
==========================================
--
2.25.1
next reply other threads:[~2021-01-28 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 15:55 qifu [this message]
2021-02-02 5:46 ` 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=20210128155539.27471-1-qi.fu@intel.com \
--to=qi.fu@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).