test suite reviews and discussions
 help / color / mirror / Atom feed
From: Hongbo Li <hongbox.li@intel.com>
To: dts@dpdk.org
Cc: Hongbo Li <hongbox.li@intel.com>
Subject: [dts][PATCH V1 1/2] test_plans/large_vf: modify script to adapt to changes in dpdk
Date: Thu,  9 Feb 2023 18:34:34 +0800	[thread overview]
Message-ID: <20230209103435.2106-1-hongbox.li@intel.com> (raw)

1.after dpdk is modified, if all ports fail to start, dpdk still allows testpmd to enter the command line, instead of unconditionally terminating testpmd.
According to dpdk commit 7e40372522c("app/testpmd: fix interactive mode with no ports").

2.after driver is modified, the default RX rings available decreased(now from SW4.2 default number of queues are created according to the single NUMA CPU cores), so modify script to adapt.

Signed-off-by: Hongbo Li <hongbox.li@intel.com>
---
 test_plans/large_vf_test_plan.rst | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/test_plans/large_vf_test_plan.rst b/test_plans/large_vf_test_plan.rst
index e043a660..0f2318de 100644
--- a/test_plans/large_vf_test_plan.rst
+++ b/test_plans/large_vf_test_plan.rst
@@ -264,25 +264,29 @@ Subcase 5: PF fdir + large VF fdir co-exist
 
 Start testpmd on VF0 with 256 queues.
 
-Create 10 rules on PF0, queue from [54~63]::
+Get RX rings available on DUT ::
 
-    ethtool -N enp96s0f0 flow-type udp4 dst-ip 192.168.0.21 src-port 22 action 63
-    ethtool -N enp96s0f0 flow-type udp4 dst-ip 192.168.0.22 src-port 22 action 62
-    ethtool -N enp96s0f0 flow-type udp4 dst-ip 192.168.0.23 src-port 22 action 61
+    ethtool -n enp96s0f0
+
+Create 10 rules on PF0, and the actions decrease from the maximum value of RX rings available::
+
+    ethtool -N enp96s0f0 flow-type udp4 dst-ip 192.168.0.21 src-port 22 action 35
+    ethtool -N enp96s0f0 flow-type udp4 dst-ip 192.168.0.22 src-port 22 action 34
+    ethtool -N enp96s0f0 flow-type udp4 dst-ip 192.168.0.23 src-port 22 action 33
     ...
-    ethtool -N enp96s0f0 flow-type udp4 dst-ip 192.168.0.30 src-port 22 action 54
+    ethtool -N enp96s0f0 flow-type udp4 dst-ip 192.168.0.30 src-port 22 action 26
 
 Check rules on PF::
 
     ethtool -n enp96s0f0
 
-Send matched patches to PF::
+Send matched packet to PF::
 
     pkt1=Ether(dst="00:00:00:00:01:00")/IP(src=RandIP(),dst="192.168.0.21")/UDP(sport=22,dport=23)/Raw('x'*80)
     ......
     pkt10=Ether(dst="00:00:00:00:01:00")/IP(src=RandIP(),dst="192.168.0.30")/UDP(sport=22,dport=23)/Raw('x'*80)
 
-Check PF matched queue [54~63] could receive matched packet::
+Check PF matched queue could receive matched packet::
 
     ethtool -S enp96s0f0
 
-- 
2.17.1


             reply	other threads:[~2023-02-09  2:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 10:34 Hongbo Li [this message]
2023-02-09 10:34 ` [dts][PATCH V1 2/2] tests/large_vf: " Hongbo Li
  -- strict thread matches above, loose matches on Subject: below --
2023-02-08 18:35 [dts][PATCH V1 1/2] test_plans/large_vf: " Hongbo Li
2023-02-08 18:22 Hongbo Li

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=20230209103435.2106-1-hongbox.li@intel.com \
    --to=hongbox.li@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).