From: hanyingya <yingyax.han@intel.com>
To: dts@dpdk.org, zhe.wan@intel.com
Cc: hanyingya <yingyax.han@intel.com>
Subject: [dts] [PATCH V1]test_plan: add packet_ordering function test plan
Date: Wed, 26 Feb 2020 15:18:15 +0800 [thread overview]
Message-ID: <1582701495-35228-1-git-send-email-yingyax.han@intel.com> (raw)
Signed-off-by: hanyingya <yingyax.han@intel.com>
---
test_plans/packet_ordering_test_plan.rst | 18 ++++++++++++++++--
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/test_plans/packet_ordering_test_plan.rst b/test_plans/packet_ordering_test_plan.rst
index a647660..cac5f7c 100644
--- a/test_plans/packet_ordering_test_plan.rst
+++ b/test_plans/packet_ordering_test_plan.rst
@@ -1,4 +1,4 @@
-.. Copyright (c) <2019>, Intel Corporation
+.. Copyright (c) <2020>, Intel Corporation
All rights reserved.
Redistribution and use in source and binary forms, with or without
@@ -88,4 +88,18 @@ Reordered ratio: ratio between out of order packets and total sent packets.
Run the app with below sample command::
- ./examples/packet_ordering/build/packet_ordering -c coremask -- -p portmask
\ No newline at end of file
+ ./examples/packet_ordering/build/packet_ordering -c coremask -- -p portmask
+
+Test Case: keep the packet ordering
+===================================
+
+This is a basic functional test.
+The packets order which will pass through a same flow should be guaranteed.
+
+1. Run the sample with below command::
+
+ ./examples/packet_ordering/build/packet_ordering -c coremask -- -p portmask
+
+2. Send 1000 packets with the same 5-tuple traffic from Scapy
+
+3. Observe the packets received and check the packets order.
--
2.17.2
next reply other threads:[~2020-02-26 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 7:18 hanyingya [this message]
2020-03-03 5:41 ` 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=1582701495-35228-1-git-send-email-yingyax.han@intel.com \
--to=yingyax.han@intel.com \
--cc=dts@dpdk.org \
--cc=zhe.wan@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).