From: Lingli Chen <linglix.chen@intel.com>
To: dts@dpdk.org
Cc: yuan.peng@intel.com, Lingli Chen <linglix.chen@intel.com>
Subject: [dts][PATCH V2 1/2] test_plans/vf_rss: add new case to test Tx queue number is more than Rx queue number
Date: Wed, 11 Jan 2023 23:36:53 -0500 [thread overview]
Message-ID: <20230112043654.53944-1-linglix.chen@intel.com> (raw)
add new case to cover test Tx queue number is more than Rx queue number
Signed-off-by: Lingli Chen <linglix.chen@intel.com>
---
| 54 +++++++++++++++++++++++++++++++++
1 file changed, 54 insertions(+)
--git a/test_plans/vf_rss_test_plan.rst b/test_plans/vf_rss_test_plan.rst
index 987f71f8..dc3b1da3 100644
--- a/test_plans/vf_rss_test_plan.rst
+++ b/test_plans/vf_rss_test_plan.rst
@@ -168,3 +168,57 @@ Before send packet, config hash reta,512(NICS with kernel driver i40e has 64 ret
after send packet, based on the testpmd output RSS hash value to calculate hash_index, then check whether the
actual receive queue is the queue configured in the reta.
+
+Test case: test rxq txq number inconsistent
+===========================================
+1. Create one VF from kernel PF::
+
+ echo 1 > /sys/bus/pci/devices/0000\:18\:00.0/sriov_numvfs
+
+2. Bind VFs to vfio-pci::
+
+ ./usertools/dpdk-devbind.py -b vfio-pci 18:01.0
+
+3. Start the testpmd with rxq not equal to txq::
+
+ ./<build_target>/app/dpdk-testpmd -l 1-9 -n 2 -- -i --rxq=4 --txq=8 --nb-core=8
+
+.. note::
+ queue pairs in number of 1, 2, 4, 8, 16, 32, 64, etc.
+ For vf of ixgbe, the maximum number of rxq and txq supported is 4.
+
+4. Set rxonly fwd, enable print, start testpmd::
+
+ testpmd> set fwd rxonly
+ testpmd> set verbose 1
+ testpmd> start
+
+5. Send different hash types' packets with different keywords, then check rx port
+ could receive packets by different queues::
+
+ sendp([Ether(dst="00:01:23:45:67:89")/IP(src="192.168.0.4", dst=RandIP())], iface="eth3")
+
+6. Check the total Rx packets in all the RxQ should be equal to the total HW Rx packets::
+
+ testpmd> show fwd stats all
+ ------- Forward Stats for RX Port= 0/Queue= 0 -> TX Port= 0/Queue= 0 -------
+ RX-packets: 252 TX-packets: 0 TX-dropped: 0
+
+ ------- Forward Stats for RX Port= 0/Queue= 1 -> TX Port= 0/Queue= 1 -------
+ RX-packets: 257 TX-packets: 0 TX-dropped: 0
+
+ ------- Forward Stats for RX Port= 0/Queue= 2 -> TX Port= 0/Queue= 2 -------
+ RX-packets: 259 TX-packets: 0 TX-dropped: 0
+
+ ------- Forward Stats for RX Port= 0/Queue= 3 -> TX Port= 0/Queue= 3 -------
+ RX-packets: 256 TX-packets: 0 TX-dropped: 0
+
+ ---------------------- Forward statistics for port 0 ----------------------
+ RX-packets: 1024 RX-dropped: 0 RX-total: 1024
+ TX-packets: 0 TX-dropped: 0 TX-total: 0
+ ----------------------------------------------------------------------------
+
+ +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
+ RX-packets: 1024 RX-dropped: 0 RX-total: 1024
+ TX-packets: 0 TX-dropped: 0 TX-total: 0
+ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--
2.17.1
next reply other threads:[~2023-01-12 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 4:36 Lingli Chen [this message]
2023-01-12 4:36 ` [dts][PATCH V2 2/2] tests/vf_rss: add case test_vf_rss_rxq_txq_inconsistent Lingli Chen
2023-01-12 9:05 ` Peng, Yuan
2023-01-13 2:46 ` lijuan.tu
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=20230112043654.53944-1-linglix.chen@intel.com \
--to=linglix.chen@intel.com \
--cc=dts@dpdk.org \
--cc=yuan.peng@intel.com \
/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).