From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>
Subject: [dts] [PATCH V1] add test plan l2fwd_jobstats
Date: Mon, 20 Feb 2017 17:08:19 +0800 [thread overview]
Message-ID: <1487581699-30545-2-git-send-email-gangx.xu@intel.com> (raw)
In-Reply-To: <1487581699-30545-1-git-send-email-gangx.xu@intel.com>
Signed-off-by: xu,gang <gangx.xu@intel.com>
---
test_plans/l2fwd_jobstats_test_plan.rst | 139 ++++++++++++++++++++++++++++++++
1 file changed, 139 insertions(+)
create mode 100644 test_plans/l2fwd_jobstats_test_plan.rst
diff --git a/test_plans/l2fwd_jobstats_test_plan.rst b/test_plans/l2fwd_jobstats_test_plan.rst
new file mode 100644
index 0000000..3d04169
--- /dev/null
+++ b/test_plans/l2fwd_jobstats_test_plan.rst
@@ -0,0 +1,139 @@
+.. Copyright (c) < 2017 >, 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.
+
+== == == == == == == == == == == == == == == == ==
+l2fwd - jobstats test plan
+== == == == == == == == == == == == == == == == ==
+
+This test plan will cover the basic l2fwd - jobstats case
+and will be worked as a regression test plan.
+
+Test Case1:
+ check different send rate the sample received rate
+== == == == == == == == == == == == == == == == == == == == == == == ==
+1. Bind two NIC port to igb_uio, then launch the l2fwd - jobstats sample
+
+ app / l2fwd - jobstats - c 0x03 - n4 - - -q 2 - p 03 - l
+ testpmd >
+
+2. Check the output, the Idle(Job) should occupy most of the CPU time
+and all statistic is zero. Like following:
+
+Port statistics == == == == == == == == == == == == == == == == == == ==
+Statistics for port 0 - -----------------------------
+Packets sent:
+ 0
+Packets received:
+ 0
+Packets dropped:
+ 0
+Statistics for port 1 - -----------------------------
+Packets sent:
+ 0
+Packets received:
+ 0
+Packets dropped:
+ 0
+Aggregate statistics == == == == == == == == == == == == == == == == == ==
+Total packets sent:
+ 0
+Total packets received:
+ 0
+Total packets dropped:
+ 0
+== == == == == == == == == == == == == == == == == == == == == == == == ==
+----------------
+LCore 0:
+ statistics(time in ns, collected in 275, 887, 870)
+Stat type total % total avg min max
+Stats duration:
+ 10, 275, 967, 160
+Loop count:
+ 304, 669
+Exec time 8, 127, 075 0.1 % 26 23 15, 956, 536
+Management time 316, 445, 834 3.1 % 1, 039 14 16, 002, 986
+Exec + management 324, 572, 909 3.2 % 1, 065 37 31, 959, 522
+Idle(job) 9, 951, 394, 251 96.8 % 47, 560 37 15, 956, 536
+
+Job 0:
+ port 0 fwd
+Exec count:
+ 101, 146
+Exec period:
+ 100, 035
+Exec time 2, 456, 268 0.0 % 24 23 843
+
+Job 1:
+ port 1 fwd
+Exec count:
+ 101, 146
+Exec period:
+ 100, 035
+Exec time 2, 469, 969 0.0 % 24 23 2, 086
+
+Job 2:
+ flush
+Exec count:
+ 102, 723
+Exec period:
+ 100, 036
+Exec time 3, 200, 838 0.0 % 31 30 471
+== == == == == == == == == == == == == == == == == == == == == == == == == ==
+
+3.Send packets to NIC port with different rate, check the core status reported
+by l2fwd - jobstats sample is correct Increase the packet send rate from 0 %
+linerateto 100 % linerate. Check the "Exec + management" percentage can increase
+with the packet rate accordingly
+
+Stat type total % total avg min max
+Stats duration:
+ 10, 275, 967, 160
+Loop count:
+ 304, 669
+Exec time 8, 127, 075 0.1 % 26 23 15, 956, 536
+Management time 316, 445, 834 3.1 % 1, 039 14 16, 002, 986
+Exec + management 324, 572, 909 3.2 % 1, 065 37 31, 959, 522
+Idle(job) 9, 951, 394, 251 96.8 % 47, 560 37 15, 956, 536
+
+
+Test Case2:
+ Check the packet statistic is correct
+== == == == == == == == == == == == == == == == == == == == == == == == == == ==
+1. Bind two NIC port to igb_uio, then launch the l2fwd - jobstats sample
+
+ app / l2fwd - jobstats - c 0x03 - n4 - - -q 2 - p 03 - l
+
+2. Send 10, 000, 000 packet to port 1 and 10, 000, 000 packets to port 2, check the
+NIC packets number reported by sample is the same with waht we set at the packet
+generator side.
--
1.9.3
prev parent reply other threads:[~2017-02-20 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 9:08 [dts] [PATCH V1] add test suite l2fwd_jobstats xu,gang
2017-02-20 9:08 ` xu,gang [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=1487581699-30545-2-git-send-email-gangx.xu@intel.com \
--to=gangx.xu@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).