test suite reviews and discussions
 help / color / mirror / Atom feed
From: Haiyang Zhao <haiyangx.zhao@intel.com>
To: dts@dpdk.org
Cc: xueqin.lin@intel.com, Haiyang Zhao <haiyangx.zhao@intel.com>
Subject: [dts] [PATCH V1 1/2] test_plans/vf_rss: delete unsupport NIC and optimize verify description.
Date: Fri, 19 Jul 2019 18:16:33 +0000	[thread overview]
Message-ID: <20190719181634.10735-1-haiyangx.zhao@intel.com> (raw)

*.for test_vfpmd_rss, it has no need to config rss reta.
*.delete niantic config rss reta description, as it not support.
*.add NICS with kernel driver i40e has 64 rss reta. 
*.add more description of verify rss reta test result.

Signed-off-by: Haiyang Zhao <haiyangx.zhao@intel.com>
---
 test_plans/vf_rss_test_plan.rst | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)

diff --git a/test_plans/vf_rss_test_plan.rst b/test_plans/vf_rss_test_plan.rst
index 746b074..0e48f46 100644
--- a/test_plans/vf_rss_test_plan.rst
+++ b/test_plans/vf_rss_test_plan.rst
@@ -150,27 +150,23 @@ interactive commands of the ``testpmd`` application.
 
     ./usertools/dpdk-devbind.py --bind=igb_uio 00:06.0 00:07.0
 
-6. Reta Configuration.  128 reta entries configuration::
-
-     testpmd command: port config 0 rss reta (hash_index,queue_id)
-
-7. Pmd fwd only receive the packets::
+6. Pmd fwd only receive the packets::
 
      testpmd command: set fwd rxonly
 
-8. Rss received package type configuration two received packet types configuration::
+7. Rss received package type configuration two received packet types configuration::
 
      testpmd command: port config all rss ip/udp/tcp
 
-9. Verbose configuration::
+8. Verbose configuration::
 
      testpmd command: set verbose 8
 
-10. Start packet receive::
+9. Start packet receive::
 
       testpmd command: start
 
-11. Send different hash types' packets with different keywords, then check rx port
+10. Send different hash types' packets with different keywords, then check rx port
     could receive packets by different queues::
 
       sendp([Ether(dst="90:e2:ba:36:99:3c")/IP(src="192.168.0.4", dst="192.168.0.5")], iface="eth3")
@@ -181,6 +177,9 @@ Test Case:  test_reta
 
 This case test hash reta table, the test steps same with test_rss_hash except config hash reta table
 
-Before send packet, config hash reta,512(niantic NICs have 128 reta) reta entries configuration::
+Before send packet, config hash reta,512(NICS with kernel driver i40e has 64 reta) reta entries configuration::
 
   testpmd command: port config 0 rss reta (hash_index,queue_id)
+
+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.
-- 
2.17.1


             reply	other threads:[~2019-07-19 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 18:16 Haiyang Zhao [this message]
2019-07-19 18:16 ` [dts] [PATCH V1 2/2] tests/vf_rss: optmize vf_pmdrss and vf_pmdrss_reta Haiyang Zhao
2019-07-22  3:11   ` Zhang, YanX A
2019-08-06 10:11   ` Tu, Lijuan
2019-08-06 10:11 ` [dts] [PATCH V1 1/2] test_plans/vf_rss: delete unsupport NIC and optimize verify description 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=20190719181634.10735-1-haiyangx.zhao@intel.com \
    --to=haiyangx.zhao@intel.com \
    --cc=dts@dpdk.org \
    --cc=xueqin.lin@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).