From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: ke1.xu@intel.com, qi.fu@intel.com, lijuan.tu@intel.com
Subject: [DTS][PATCH V3 2/2] test_plans/vf_offload: format packet organization of previous cases into a table
Date: Tue, 13 Dec 2022 17:01:41 +0800 [thread overview]
Message-ID: <20221213090141.170959-3-ke1.xu@intel.com> (raw)
In-Reply-To: <20221213090141.170959-1-ke1.xu@intel.com>
Format the packet organization into a table to make it better organized to
read.
Signed-off-by: Ke Xu <ke1.xu@intel.com>
---
test_plans/vf_offload_test_plan.rst | 30 +++++++++++++++++++++++++++--
1 file changed, 28 insertions(+), 2 deletions(-)
diff --git a/test_plans/vf_offload_test_plan.rst b/test_plans/vf_offload_test_plan.rst
index f80290f5..00b221ca 100644
--- a/test_plans/vf_offload_test_plan.rst
+++ b/test_plans/vf_offload_test_plan.rst
@@ -102,7 +102,21 @@ Enable the IPv4/UDP/TCP/SCTP HW checksum offload on port 0::
TX threshold registers: pthresh=32 hthresh=8 wthresh=8
Configure the traffic generator to send the multiple packets for the following
-combination: IPv4/UDP, IPv4/TCP, IPv4/SCTP, IPv6/UDP, IPv6/TCP.
+combination:
+
+ +----------------+----------------------------------------+
+ | packet type | packet organization |
+ +================+========================================+
+ | | Ether / IPv4 / UDP / payload |
+ | +----------------------------------------+
+ | | Ether / IPv4 / TCP / payload |
+ | +----------------------------------------+
+ | packets | Ether / IPv4 / SCTP / payload |
+ | for checksum +----------------------------------------+
+ | offload test | Ether / IPv6 / UDP / payload |
+ | +----------------------------------------+
+ | | Ether / IPv6 / TCP / payload |
+ +----------------+----------------------------------------+
Send packets with incorrect checksum,
verify dpdk can rx it and report the checksum error,
@@ -237,7 +251,19 @@ Enable the IPv4/UDP/TCP/SCTP SW checksum offload on port 0::
TX threshold registers: pthresh=32 hthresh=8 wthresh=8
Configure the traffic generator to send the multiple packets for the following
-combination: IPv4/UDP, IPv4/TCP, IPv6/UDP, IPv6/TCP.
+combination:
+
+ +----------------+----------------------------------------+
+ | packet type | packet organization |
+ +================+========================================+
+ | | Ether / IPv4 / UDP / payload |
+ | +----------------------------------------+
+ | packets | Ether / IPv4 / TCP / payload |
+ | for checksum +----------------------------------------+
+ | offload test | Ether / IPv6 / UDP / payload |
+ | +----------------------------------------+
+ | | Ether / IPv6 / TCP / payload |
+ +----------------+----------------------------------------+
Send packets with incorrect checksum,
verify dpdk can rx it and report the checksum error,
--
2.25.1
next prev parent reply other threads:[~2022-12-13 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 9:01 [DTS][PATCH V3 0/2] update existing cases and add new cases to validate vf tunneling packets Ke Xu
2022-12-13 9:01 ` [DTS][PATCH V3 1/2] test_plans/vf_offload: add test cases for " Ke Xu
2022-12-13 9:01 ` Ke Xu [this message]
2022-12-26 5:25 ` [DTS][PATCH V3 2/2] test_plans/vf_offload: format packet organization of previous cases into a table 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=20221213090141.170959-3-ke1.xu@intel.com \
--to=ke1.xu@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=qi.fu@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).