From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>
Subject: [dts] [PATCH V2 04/10] add ip_pipeline cpu utilization test plan
Date: Thu, 25 Aug 2016 16:24:17 +0800 [thread overview]
Message-ID: <1472113463-4298-4-git-send-email-gangx.xu@intel.com> (raw)
In-Reply-To: <1472113463-4298-1-git-send-email-gangx.xu@intel.com>
Signed-off-by: xu,gang <gangx.xu@intel.com>
---
.../ip_pipeline_cpu_utilization_test_plan.rst | 50 ++++++++++++++++++++++
1 file changed, 50 insertions(+)
create mode 100644 test_plans/ip_pipeline_cpu_utilization_test_plan.rst
diff --git a/test_plans/ip_pipeline_cpu_utilization_test_plan.rst b/test_plans/ip_pipeline_cpu_utilization_test_plan.rst
new file mode 100644
index 0000000..d7ae39a
--- /dev/null
+++ b/test_plans/ip_pipeline_cpu_utilization_test_plan.rst
@@ -0,0 +1,50 @@
+.. BSD LICENSE
+ Copyright(c) 2010-2016 Intel Corporation. All rights reserved.
+ 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.
+
+ip_pipeline_cpu_utilization_test_plan
+======================================
+
+the ip_pipeline_cpu_utilization is test ip_pipeline cpu tx/rx packet utilization.
+steps as follow:
+
+make::
+ make -C examples/ip_pipeline/
+running::
+ ./build/ip_pipeline -p 0xf -f ./config/edge_router_downstream.cfg -s ./config/edge_router_downstream.sh
+
+send packet::
+ with the tools you can send a packet
+check::
+ ip_pipeline> t 1 headroom
+
+check the log ,if 100% the test pass ,else fail
+
+
+
--
1.9.3
next prev parent reply other threads:[~2016-08-25 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 8:24 [dts] [PATCH V2 01/10] add ip_pipeline cfg test code xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 02/10] add ip_pipeline cfg test plan xu,gang
2016-08-26 1:28 ` Liu, Yong
2016-08-25 8:24 ` [dts] [PATCH V2 03/10] add ip_pipeline cpu utilization test code xu,gang
2016-08-25 8:24 ` xu,gang [this message]
2016-08-25 8:24 ` [dts] [PATCH V2 05/10] add ip_pipeline link_identification " xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 06/10] add ip_pipeline link_identification test plan xu,gang
2016-08-26 2:19 ` Liu, Yong
2016-08-25 8:24 ` [dts] [dst][PATCH V2 07/10] add ip_pipeline parser_cleanup test code xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 08/10] add ip_pipeline parser_cleanup test plan xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 09/10] add ip_pipeline source_sink test code xu,gang
2016-08-25 8:24 ` [dts] [PATCH V2 10/10] add ip_pipeline source_sink test plan xu,gang
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=1472113463-4298-4-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).