From: Lijuan Tu <lijuan.tu@intel.com>
To: yux.jiang@intel.com
Cc: dts@dpdk.org, Lijuan Tu <lijuan.tu@intel.com>
Subject: [PATCH] test_plans/sw_hw_thash_consistence: remove test plan due to dpdk code(rte_hash) doesn't upstream
Date: Wed, 23 Mar 2022 15:55:14 +0800 [thread overview]
Message-ID: <20220323075514.2004075-1-lijuan.tu@intel.com> (raw)
Signed-off-by: Yu Jiang <yux.jiang@intel.com>
Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
---
test_plans/index.rst | 1 -
.../sw_hw_thash_consistence_test_plan.rst | 74 -------------------
2 files changed, 75 deletions(-)
delete mode 100644 test_plans/sw_hw_thash_consistence_test_plan.rst
diff --git a/test_plans/index.rst b/test_plans/index.rst
index a603b1af..054d682c 100644
--- a/test_plans/index.rst
+++ b/test_plans/index.rst
@@ -161,7 +161,6 @@ The following are the test plans for the DPDK DTS automated test system.
short_live_test_plan
shutdown_api_test_plan
speed_capabilities_test_plan
- sw_hw_thash_consistence_test_plan
vhost_cbdma_test_plan
vhost_user_interrupt_test_plan
sriov_kvm_test_plan
diff --git a/test_plans/sw_hw_thash_consistence_test_plan.rst b/test_plans/sw_hw_thash_consistence_test_plan.rst
deleted file mode 100644
index a263b3d2..00000000
--- a/test_plans/sw_hw_thash_consistence_test_plan.rst
+++ /dev/null
@@ -1,74 +0,0 @@
-.. Copyright (c) <2020>, Intel Corporation
- All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- - Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
-
- - Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in
- the documentation and/or other materials provided with the
- distribution.
-
- - Neither the name of Intel Corporation nor the names of its
- contributors may be used to endorse or promote products derived
- from this software without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
- "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
- LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
- FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
- COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
- (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
- SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
- STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
- ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
- OF THE POSSIBILITY OF SUCH DAMAGE.
-
-======================================================
-Software/hardware Toeplitz hash consistence test suite
-======================================================
-
-This test suite is to check if the Toeplitz hash by hardware (NIC) is consistence
-with by software (rte_hash)
-
-First apply a DPDK patch, which provide an example for calling rte_hash ::
-
- cd <dpdk>
- git apply <dts>/dep/0001-Generate-an-example-for-calling-thash-lib.patch
-
-Compile the example ::
-
- export RTE_SDK=<dpdk>
- cd <dpdk>/examples/thash
- make
-
-Run thash example, which supported format: thash_test TYPE(ipv4|ipv4-udp|ipv4-tcp) IP_DST IP_SRC PORT_DST PORT_SRC ::
-
- ./build/thash_test ipv6 ::22 ::11 1234 4321
- # The output
- ipv6
- ::22
- ::11
- 1234
- 4321
-
- Hash value = 914e08e4
-
-Then, configure the NIC and send packets to the NIC, expect the hash value by NIC is same to thash_test ::
-
- # Launch testpmd, and configure the hash key
- testpmd> set verbose 1
- testpmd> start
- testpmd> port config 0 rss-hash-key ipv6 1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd
- # Send packet to testpmd's interface
- sendp(Ether(dst="52:36:30:A0:73:69")/IPv6(dst="::22",src="::11"),iface='ens801f1')
- # The RSS hash value is same to thash_test result
- port 0/queue 4: received 1 packets
- src=00:00:00:00:00:00 - dst=52:36:30:A0:73:69 - type=0x86dd - length=60 - nb_segs=1 - RSS hash=0x914e08e4 - RSS queue=0x4 - sw ptype: L2_ETHER L3_IPV6 - l2_len=14 - l3_len=40 - Receive queue=0x4
- ol_flags: PKT_RX_RSS_HASH PKT_RX_L4_CKSUM_GOOD PKT_RX_IP_CKSUM_GOOD PKT_RX_OUTER_L4_CKSUM_UNKNOWN
--
2.25.1
reply other threads:[~2022-03-23 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220323075514.2004075-1-lijuan.tu@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yux.jiang@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).