test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yan Xia <yanx.xia@intel.com>
To: dts@dpdk.org
Cc: Yan Xia <yanx.xia@intel.com>
Subject: [dts] [PATCH V1] fortville_rss_granularity_config_test_plan: remove test plan of test_dual_vlan
Date: Tue, 27 Jul 2021 17:02:28 +0000	[thread overview]
Message-ID: <20210727170228.10208-1-yanx.xia@intel.com> (raw)

remove test plan of test_dual_vlan because of moving it to test_plan_generic_flow_api

Signed-off-by: Yan Xia <yanx.xia@intel.com>
---
 ...ville_rss_granularity_config_test_plan.rst | 62 -------------------
 1 file changed, 62 deletions(-)

diff --git a/test_plans/fortville_rss_granularity_config_test_plan.rst b/test_plans/fortville_rss_granularity_config_test_plan.rst
index c77f7e8a..18592b1e 100644
--- a/test_plans/fortville_rss_granularity_config_test_plan.rst
+++ b/test_plans/fortville_rss_granularity_config_test_plan.rst
@@ -247,68 +247,6 @@ and using scapy to send packets with ipv6-udp on tester::
 
 and the test result should be same as Test Case 2.
 
-Test Case 5: test dual vlan(QinQ)
-=================================
-
-1. config testpmd on DUT
-
-   1. set up testpmd with Fortville NICs::
-
-         ./testpmd -c 0x1ffff -n 4 -- -i --coremask=0x1fffe --portmask=0x1 --rxq=16 --txq=16 --tx-offloads=0x8fff
-
-   2. set qinq on::
-
-         testpmd> vlan set qinq on <port_id>
-
-   3. Reta Configuration(optional, if not set, will use default)::
-
-         testpmd> port config 0 rss reta (hash_index,queue_id)
-
-   4. PMD fwd only receive the packets::
-
-         testpmd> set fwd rxonly
-
-   5. verbose configuration::
-
-         testpmd> set verbose 8
-
-   6. start packet receive::
-
-         testpmd> start
-
-   7. rss received package type configuration::
-
-         testpmd> port config all rss ether
-
-2. using scapy to send packets with dual vlan (QinQ) on tester::
-
-
-      sendp([Ether(dst="00:00:00:00:01:00")/Dot1Q(id=0x8100,vlan=1)/Dot1Q(id=0x8100,vlan=2)], iface=tester_itf)
-
-   then got hash value and queue value that output from the testpmd on DUT.
-
-3. set hash input set to "none" by testpmd on dut::
-
-
-      testpmd> set_hash_input_set 0 l2_payload none select
-
-   send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the value should be
-   same with the values in step 2.
-
-4. set hash input set by testpmd on dut, enable ovlan field::
-
-
-      testpmd> set_hash_input_set 0 l2_payload ovlan add
-
-   send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the value should be
-   different with the values in step 2.
-
-5. set hash input set by testpmd on dut, enable ovlan, ivlan field::
-
-      testpmd> set_hash_input_set 0 l2_payload ivlan add
-
-   send packet as step 2, got hash value and queue value that output from the testpmd on DUT, the value should be
-   different with the values in step 2 & step 4.
 
 Test Case 6: 32-bit GRE keys and 24-bit GRE keys test
 =====================================================
-- 
2.17.1


             reply	other threads:[~2021-07-27  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 17:02 Yan Xia [this message]
2021-07-27  9:19 ` Peng, Yuan
2021-07-29 11:39   ` 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=20210727170228.10208-1-yanx.xia@intel.com \
    --to=yanx.xia@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).