From: Song Jiale <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Song Jiale <songx.jiale@intel.com>
Subject: [dts] [PATCH V2 1/2] test_plans/ipv4_reassembly: modify script to adapt changes in dpdk
Date: Mon, 20 Mar 2023 18:05:02 +0000 [thread overview]
Message-ID: <20230320180503.3307034-2-songx.jiale@intel.com> (raw)
In-Reply-To: <20230320180503.3307034-1-songx.jiale@intel.com>
DPDK increase default value for config parameter RTE_LIBRTE_IP_FRAG_MAX_FRAG from 4 to 8.
Modify the script to adapt to this change.
According to dpdk commit f8e0f8ce90303b("ip_frag: increase default maximum of fragments").
Signed-off-by: Song Jiale <songx.jiale@intel.com>
---
test_plans/ipv4_reassembly_test_plan.rst | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/test_plans/ipv4_reassembly_test_plan.rst b/test_plans/ipv4_reassembly_test_plan.rst
index 7f721123..43d18590 100644
--- a/test_plans/ipv4_reassembly_test_plan.rst
+++ b/test_plans/ipv4_reassembly_test_plan.rst
@@ -153,12 +153,11 @@ Sample command::
./<build_target>/examples/dpdk-ip_reassembly -c 0x2 -n 4 -- \
-P -p 0x2 --config "(1,0,1)" --maxflows=1024 --flowttl=10s
-Sends 1 packet split in 5 fragments while the maximum number of supported
-fragments per packet is 4.
+Sends 1 frame split in into maximum fragments + 1 fragment, the packet can't be forwarded back.
It expects:
- - 5 IP packets to be sent to the DUT.
+ - (maximum fragments + 1 fragment) IP packets to be sent to the DUT.
- 0 TCP packets being forwarded back to the TESTER.
- 0 packets with a valid TCP checksum.
--
2.25.1
next prev parent reply other threads:[~2023-03-20 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 18:05 [dts] [PATCH V2 0/2] " Song Jiale
2023-03-20 18:05 ` Song Jiale [this message]
2023-03-20 18:05 ` [dts] [PATCH V2 2/2] tests/ipv4_reassembly: " Song Jiale
2023-03-21 6:10 ` Peng, Yuan
2023-03-28 1:04 ` 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=20230320180503.3307034-2-songx.jiale@intel.com \
--to=songx.jiale@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).