test suite reviews and discussions
 help / color / mirror / Atom feed
From: "huilong,xu" <huilongx.xu@intel.com>
To: dts@dpdk.org
Cc: jingguox.fu@intel.com
Subject: [dts] [dts 2/3] [PATCH V1] add queue start stop test plan
Date: Fri, 29 May 2015 16:39:45 +0800	[thread overview]
Message-ID: <1432888786-25354-2-git-send-email-huilongx.xu@intel.com> (raw)
In-Reply-To: <1432888786-25354-1-git-send-email-huilongx.xu@intel.com>

From: huilong xu <huilongx.xu@intel.com>


Signed-off-by: huilong xu <huilongx.xu@intel.com>
---
 test_plans/queue_start_stop_test_plan.rst |   75 +++++++++++++++++++++++++++++
 1 files changed, 75 insertions(+), 0 deletions(-)
 create mode 100644 test_plans/queue_start_stop_test_plan.rst

diff --git a/test_plans/queue_start_stop_test_plan.rst b/test_plans/queue_start_stop_test_plan.rst
new file mode 100644
index 0000000..5dd99cc
--- /dev/null
+++ b/test_plans/queue_start_stop_test_plan.rst
@@ -0,0 +1,75 @@
+# BSD LICENSE
+#
+# Copyright(c) 2010-2015 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.
+
+
+======================================
+Intel. DPDK Shutdown API Feature Tests
+======================================
+
+This tests for Shutdown API feature can be run on linux userspace. It
+will check if NIC port can be stopped and restarted without exiting the
+application process. Furthermore, it will check if it can reconfigure
+new configurations for a port after the port is stopped, and if it is
+able to restart with those new configurations. It is based on testpmd
+application.
+
+The test is performed by running the testpmd application and using a
+traffic generator. Port/queue configurations can be set interactively,
+and still be set at the command line when launching the application in
+order to be compatible with previous test framework.
+
+Prerequisites
+-------------
+
+Assume port A and B are connected to the remote ports, e.g. packet generator.
+To run the testpmd application in linuxapp environment with 4 lcores,
+4 channels with other default parameters in interactive mode.
+
+        $ ./testpmd -c 0xf -n 4 -- -i
+
+Test Case: queue start/stop
+---------------------------------------
+this case support PF (fortville), VF(fortville,niantic)
+1. update testpmd source code. add a C code "printf("ports %u queue %u revice %u packages\n", fs->rx_port, fs->rx_queue, nb_rx)".
+in ./app/test-pmd/fwdmac.c
+2. compile testpmd again, then run testpmd.
+3. run "set fwd mac" to set fwd type
+4. run "start" to start fwd package
+5. start packet generator to transmit and receive packets
+6. run "port 0 rxq 0 stop" to stop rxq 0 in port 0
+7. start packet generator to transmit and not receive packets
+8. run "port 0 rxq 0 start" to start rxq 0 in port 0
+9. run "port 1 txq 1 stop" to start txq 0 in port 1
+10. start packet generator to transmit and not receive packets but in testpmd it is a "ports 0 queue 0 revice 1 packages" print
+11. run "port 1 txq 1 start" to start txq 0 in port 1
+12  start packet generator to transmit and receive packets
+13 test it again with VF
+successfully  
-- 
1.7.4.4

  reply	other threads:[~2015-05-29  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  8:39 [dts] [dts 1/3] [PATCH V1] add queue start/stop test for forvtille huilong,xu
2015-05-29  8:39 ` huilong,xu [this message]
2015-06-08  1:55   ` [dts] [dts 2/3] [PATCH V1] add queue start stop test plan Fu, JingguoX
2015-05-29  8:39 ` [dts] [dts 3/3] [PATCH V1] add queue start queue test code huilong,xu
2015-06-08  1:55   ` Fu, JingguoX
2015-06-01  9:21 ` [dts] [dts 1/3] [PATCH V1] add queue start/stop test for forvtille Liu, Yong
2015-06-08  1:54 ` Fu, JingguoX

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=1432888786-25354-2-git-send-email-huilongx.xu@intel.com \
    --to=huilongx.xu@intel.com \
    --cc=dts@dpdk.org \
    --cc=jingguox.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).