From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: ke1.xu@intel.com, qi.fu@intel.com, lijuan.tu@intel.com,
yux.jiang@intel.com, zhiminx.huang@intel.com
Subject: [DTS][PATCH V4 5/5] test_plans/vf_offload: add VLAN packets to test scope and improve vector path validating.
Date: Tue, 14 Feb 2023 14:28:40 +0800 [thread overview]
Message-ID: <20230214062840.2434213-6-ke1.xu@intel.com> (raw)
In-Reply-To: <20230214062840.2434213-1-ke1.xu@intel.com>
Add VLAN Packets to ensure checksum offload works well on packets with Dot1Q part.
For daily regression, we introduce wrapped cases for each path.
Signed-off-by: Ke Xu <ke1.xu@intel.com>
---
test_plans/vf_offload_test_plan.rst | 158 ++++++++++++++++++++++++++++
1 file changed, 158 insertions(+)
diff --git a/test_plans/vf_offload_test_plan.rst b/test_plans/vf_offload_test_plan.rst
index 3e9b658b..1c929371 100644
--- a/test_plans/vf_offload_test_plan.rst
+++ b/test_plans/vf_offload_test_plan.rst
@@ -286,6 +286,135 @@ be validated as pass by the tester.
The first byte of source IPv4 address will be increased by testpmd. The checksum
is indeed recalculated by software algorithms.
+
+Test Case: HW checksum offload check with vlan
+==============================================
+Start testpmd and enable checksum offload on rx port. Based on test steps of
+HW checksum offload check, configure the traffic generator to send the multiple
+packets for the following combination:
+
+ +----------------+----------------------------------------+
+ | packet type | packet organization |
+ +================+========================================+
+ | | Ether / VLAN / IPv4 / UDP / payload |
+ | +----------------------------------------+
+ | | Ether / VLAN / IPv4 / TCP / payload |
+ | +----------------------------------------+
+ | packets | Ether / VLAN / IPv4 / SCTP / payload |
+ | for checksum +----------------------------------------+
+ | offload test | Ether / VLAN / IPv6 / UDP / payload |
+ | +----------------------------------------+
+ | | Ether / VLAN / IPv6 / TCP / payload |
+ +----------------+----------------------------------------+
+
+
+Test Case: HW tunneling checksum offload check with vlan
+========================================================
+Based on test steps of HW tunneling checksum offload check, configure the
+traffic generator to send the multiple packets combination with outer or
+tunneling package of:
+
+ +----------------+--------------------------------------------+
+ | packet type | packet organization |
+ +================+============================================+
+ | | Ether / VLAN / IPv4 / UDP / VXLAN / Ether |
+ | +--------------------------------------------+
+ | | Ether / VLAN / IPv6 / UDP / VXLAN / Ether |
+ | +--------------------------------------------+
+ | | Ether / VLAN / IPv4 / GRE |
+ | outer and +--------------------------------------------+
+ | tunneling | Ether / VLAN / IPv4 / GRE / Ether |
+ | packets +--------------------------------------------+
+ | for checksum | Ether / VLAN / IPv6 / GRE |
+ | offload test +--------------------------------------------+
+ | | Ether / VLAN / IPv6 / GRE / Ether |
+ | +--------------------------------------------+
+ | | Ether / VLAN / IPv4 / NVGRE |
+ | +--------------------------------------------+
+ | | Ether / VLAN / IPv4 / NVGRE / Ether |
+ | +--------------------------------------------+
+ | | Ether / VLAN / IPv6 / NVGRE |
+ | +--------------------------------------------+
+ | | Ether / VLAN / IPv6 / NVGRE / Ether |
+ | +--------------------------------------------+
+ | | Ether / VLAN / IPv4 / UDP / GTPU |
+ | +--------------------------------------------+
+ | | Ether / VLAN / IPv6 / UDP / GTPU |
+ +----------------+--------------------------------------------+
+
+
+Test Case: HW checksum offload check on scalar path
+===================================================
+These set of cases based on existing cases are designed for better case managment for
+regression test.
+
+Start testpmd with eal parameter --force-max-simd-bitwidth=64. Based on test steps of
+'HW checksum offload check'.
+
+Test Case: HW checksum offload check on sse path
+================================================
+Start testpmd with eal parameter --force-max-simd-bitwidth=128. Based on test steps of
+'HW checksum offload check'.
+
+Test Case: HW checksum offload check on avx2 path
+=================================================
+Start testpmd with eal parameter --force-max-simd-bitwidth=256. Based on test steps of
+'HW checksum offload check'.
+
+Test Case: HW checksum offload check on avx512 path
+===================================================
+Start testpmd with eal parameter --force-max-simd-bitwidth=512. Based on test steps of
+'HW checksum offload check'.
+
+Test Case: HW checksum offload check with vlan on scalar path
+=============================================================
+
+Test Case: HW checksum offload check with vlan on sse path
+=============================================================
+
+Test Case: HW checksum offload check with vlan on avx2 path
+=============================================================
+
+Test Case: HW checksum offload check with vlan on avx512 path
+=============================================================
+
+Test Case: HW tunneling checksum offload check on scalar path
+=============================================================
+
+Test Case: HW tunneling checksum offload check on sse path
+==========================================================
+
+Test Case: HW tunneling checksum offload check on avx2 path
+===========================================================
+
+Test Case: HW tunneling checksum offload check on avx512 path
+=============================================================
+
+Test Case: HW tunneling checksum offload check with vlan on scalar path
+=======================================================================
+
+Test Case: HW tunneling checksum offload check with vlan on sse path
+====================================================================
+
+Test Case: HW tunneling checksum offload check with vlan on avx2 path
+=====================================================================
+
+Test Case: HW tunneling checksum offload check with vlan on avx512 path
+=======================================================================
+
+Test Case: SW checksum offload check on scalar path
+===================================================
+
+Test Case: SW checksum offload check on sse path
+================================================
+
+Test Case: SW checksum offload check on avx2 path
+=================================================
+
+Test Case: SW checksum offload check on avx512 path
+===================================================
+
+
Prerequisites for TSO
=====================
@@ -510,3 +639,32 @@ Test IPv6() in scapy::
for one_outer_packet in outer_packet_list:
sendp([Ether(dst="%s", src="52:00:00:00:00:00")/one_outer_packet/IPv6(src="FE80:0:0:0:200:1FF:FE00:200", dst="3555:5555:6666:6666:7777:7777:8888:8888")/TCP(sport=1021,dport=1021)/Raw(load=RandString(size=%s))], iface="%s", count = %s)
+
+Test case: csum fwd engine, use TSO, on scalar path
+===================================================
+These set of cases based on existing cases are designed for better case managment for
+regression test.
+
+Start testpmd with eal parameter --force-max-simd-bitwidth=64. Based on test steps of
+'csum fwd engine, use TSO'.
+
+Test case: csum fwd engine, use TSO, on sse path
+================================================
+
+Test case: csum fwd engine, use TSO, on avx2 path
+=================================================
+
+Test case: csum fwd engine, use TSO, on avx512 path
+===================================================
+
+Test case: csum fwd engine, use tunnel TSO, on scalar path
+==========================================================
+
+Test case: csum fwd engine, use tunnel TSO, on sse path
+=======================================================
+
+Test case: csum fwd engine, use tunnel TSO, on avx2 path
+========================================================
+
+Test case: csum fwd engine, use tunnel TSO, on avx512 path
+==========================================================
--
2.25.1
prev parent reply other threads:[~2023-02-14 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 6:28 [DTS][PATCH V4 0/5] Update vf_offload cases for DPDK-v23.03 validation Ke Xu
2023-02-14 6:28 ` [DTS][PATCH V4 1/5] tests/vf_offload: add VLAN packets to test scope Ke Xu
2023-02-14 6:28 ` [DTS][PATCH V4 2/5] tests/vf_offload: improve TSO validating Ke Xu
2023-02-14 6:28 ` [DTS][PATCH V4 3/5] tests/vf_offload: improve vector path validating Ke Xu
2023-02-14 6:28 ` [DTS][PATCH V4 4/5] tests/vf_offload: fix error when no packet captured Ke Xu
2023-02-14 6:28 ` Ke Xu [this message]
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=20230214062840.2434213-6-ke1.xu@intel.com \
--to=ke1.xu@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=qi.fu@intel.com \
--cc=yux.jiang@intel.com \
--cc=zhiminx.huang@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).