From: Yinan <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Wang Yinan <yinan.wang@intel.com>
Subject: [dts] [PATCH v1] test_plans: add test plan for vhost 1024 ethports test
Date: Thu, 27 Jun 2019 19:47:47 +0000 [thread overview]
Message-ID: <20190627194747.93307-1-yinan.wang@intel.com> (raw)
From: Wang Yinan <yinan.wang@intel.com>
Signed-off-by: Wang Yinan <yinan.wang@intel.com>
---
test_plans/vhost_1024_ethports_test_plan.rst | 57 ++++++++++++++++++++
1 file changed, 57 insertions(+)
create mode 100644 test_plans/vhost_1024_ethports_test_plan.rst
diff --git a/test_plans/vhost_1024_ethports_test_plan.rst b/test_plans/vhost_1024_ethports_test_plan.rst
new file mode 100644
index 0000000..636ddf5
--- /dev/null
+++ b/test_plans/vhost_1024_ethports_test_plan.rst
@@ -0,0 +1,57 @@
+.. Copyright (c) <2019>, 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.
+
+=============================
+vhost 1024 ethports test plan
+=============================
+
+This test plan test function of launch vhost with 1024 ethports.
+
+Test Case1: Basic test for launch vhost with 1024 ethports
+===========================================================
+
+1. SW preparation: change "CONFIG_RTE_MAX_ETHPORTS" to 1024 in DPDK configure file::
+
+ vi ./config/common_base
+ -CONFIG_RTE_MAX_ETHPORTS=32
+ +CONFIG_RTE_MAX_ETHPORTS=1024
+
+2. Launch vhost with 1024 vdev::
+
+ ./testpmd -c 0x3000 -n 4 --socket-mem 10240,10240 --file-prefix=vhost --vdev 'eth_vhost0,iface=vhost-net,queues=1' \
+ --vdev 'eth_vhost1,iface=vhost-net1,queues=1' ... -- -i # only list two vdev, here ommit other 1022 vdevs, from eth_vhost2 to eth_vhost1023
+
+3. Change "CONFIG_RTE_MAX_ETHPORTS" back to 32 in DPDK configure file::
+
+ vi ./config/common_base
+ +CONFIG_RTE_MAX_ETHPORTS=32
+ -CONFIG_RTE_MAX_ETHPORTS=1024
\ No newline at end of file
--
2.17.1
next reply other threads:[~2019-06-28 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 19:47 Yinan [this message]
2019-07-10 6:17 ` 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=20190627194747.93307-1-yinan.wang@intel.com \
--to=yinan.wang@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).