test suite reviews and discussions
 help / color / mirror / Atom feed
From: Zhimin Huang <zhiminx.huang@intel.com>
To: dts@dpdk.org
Cc: Zhimin Huang <zhiminx.huang@intel.com>
Subject: [dts] [PATCH V1 1/4] test_plans/kernelpf_iavf_test_plan:rich test point in plan
Date: Wed,  8 Sep 2021 03:13:16 +0800	[thread overview]
Message-ID: <20210907191319.15494-2-zhiminx.huang@intel.com> (raw)
In-Reply-To: <20210907191319.15494-1-zhiminx.huang@intel.com>

add some new test point in plan:
kernelpf_iavf:
 add remove mac test.
 add check rss reta changed.
 add rss hash key test.

Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
---
 test_plans/kernelpf_iavf_test_plan.rst | 94 +++++++++++++++++++++++---
 1 file changed, 85 insertions(+), 9 deletions(-)

diff --git a/test_plans/kernelpf_iavf_test_plan.rst b/test_plans/kernelpf_iavf_test_plan.rst
index 31ba975..e0360d2 100644
--- a/test_plans/kernelpf_iavf_test_plan.rst
+++ b/test_plans/kernelpf_iavf_test_plan.rst
@@ -105,6 +105,27 @@ packets can be received and forwarded by the VF::
 Use scapy to send 100 random packets with a wrong MAC to VF0, verify the
 packets can't be received by the VF.
 
+Remove the MAC 00:11:22:33:44:55::
+
+    testpmd> mac_addr remove 0 00:11:22:33:44:55
+
+Use scapy to send 100 random packets with removed VF0's MAC, verify the
+packets can't be received and forwarded by the VF::
+
+Set the defaul mac address to other mac, check the mac address has be changed
+to new set mac::
+
+    testpmd> mac_addr set 0 00:01:23:45:67:11
+    testpmd> show port info 0
+
+Use scapy to send 100 random packets with original VF0's MAC, verify the
+packets can't be received and forwarded by the VF
+
+Use scapy to send 100 random packets with new set VF0's MAC, verify the
+packets can be received and forwarded by the VF
+
+Reset to original mac address
+
 Note::
     Not set VF MAC from kernel PF for this case, if set, will print
     "not permitted error" when add new MAC for VF.
@@ -350,17 +371,35 @@ Start command with multi-queues like below::
 
    ./testpmd -c f -n 4 -- -i --txq=4 --rxq=4
 
+Show RSS RETA configuration::
+
+    testpmd> show port 0 rss reta 64 (0xffffffffffffffff)
+
+    RSS RETA configuration: hash index=0, queue=0
+    RSS RETA configuration: hash index=1, queue=1
+    RSS RETA configuration: hash index=2, queue=2
+    RSS RETA configuration: hash index=3, queue=3
+    ...
+    RSS RETA configuration: hash index=60, queue=0
+    RSS RETA configuration: hash index=61, queue=1
+    RSS RETA configuration: hash index=62, queue=2
+    RSS RETA configuration: hash index=63, queue=3
+
 Config hash reta table::
 
-  testpmd> port config 0 rss reta (0,0)
-  testpmd> port config 0 rss reta (1,1)
-  testpmd> port config 0 rss reta (2,2)
-  testpmd> port config 0 rss reta (3,3)
-  ...
-  testpmd> port config 0 rss reta (60,0)
-  testpmd> port config 0 rss reta (61,1)
-  testpmd> port config 0 rss reta (62,2)
-  testpmd> port config 0 rss reta (63,3)
+    testpmd> port config 0 rss reta (0,3)
+    testpmd> port config 0 rss reta (1,2)
+    testpmd> port config 0 rss reta (2,1)
+    testpmd> port config 0 rss reta (3,0)
+
+Check RSS RETA configuration has changed::
+
+    testpmd> show port 0 rss reta 64 (0xffffffffffffffff)
+
+    RSS RETA configuration: hash index=0, queue=3
+    RSS RETA configuration: hash index=1, queue=2
+    RSS RETA configuration: hash index=2, queue=2
+    RSS RETA configuration: hash index=3, queue=1
 
 Enable IP/TCP/UDP RSS::
 
@@ -369,6 +408,43 @@ Enable IP/TCP/UDP RSS::
 Send different flow types' IP/TCP/UDP packets to VF port, check packets are
 received by different configured queues.
 
+Test case: VF RSS hash key
+==========================
+
+Start command with multi-queues like below::
+
+   ./testpmd -c f -n 4 -- -i --txq=4 --rxq=4
+
+Show port rss hash key::
+
+    testpmd> show port 0 rss-hash key
+
+Set rxonly fwd, enable print, start testpmd::
+
+    testpmd> set fwd rxonly
+    testpmd> set verbose 1
+    testpmd> start
+
+Send ipv4 packets, mark the RSS hash value::
+
+    p=Ether(dst="56:0A:EC:50:A4:28")/IP(src="1.2.3.4")/Raw(load='X'*30)
+
+Update ipv4 different hash key::
+
+    testpmd> port config 0 rss-hash-key ipv4 1b9d58a4b961d9cd1c56ad1621c3ad51632c16a5d16c21c3513d132c135d132c13ad1531c23a51d6ac49879c499d798a7d949c8a
+
+Show port rss hash key, check the key is same to configured key::
+
+    testpmd> show port 0 rss-hash key
+    RSS functions:
+     all ipv4 ipv6 ip
+    RSS key:
+    1B9D58A4B961D9CD1C56AD1621C3AD51632C16A5D16C21C3513D132C135D132C13AD1531C23A51D6AC49879C499D798A7D949C8A
+
+Send ipv4 packets, check RSS hash value is different::
+
+    p=Ether(dst="56:0A:EC:50:A4:28")/IP(src="1.2.3.4")/Raw(load='X'*30)
+
 
 Test case: VF HW checksum offload
 =================================
-- 
2.17.1


  reply	other threads:[~2021-09-07 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 19:13 [dts] [PATCH V1 0/4] add plan and case Zhimin Huang
2021-09-07 19:13 ` Zhimin Huang [this message]
2021-09-07 19:13 ` [dts] [PATCH V1 2/4] test_plans/stats_checks_test_plan:rich test point in plan Zhimin Huang
2021-09-07 19:13 ` [dts] [PATCH V1 3/4] tests/kernelpf_iavf:rich test point in case Zhimin Huang
2021-09-07 19:13 ` [dts] [PATCH V1 4/4] tests/stats_checks:rich " Zhimin Huang

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=20210907191319.15494-2-zhiminx.huang@intel.com \
    --to=zhiminx.huang@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).