From: Yinan <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Wang Yinan <yinan.wang@intel.com>
Subject: [dts] [PATCH v1] test_plans/pvp_virtio_user_2M_hugepages: add test plan for 2M huagepage test with virtio-user
Date: Tue, 21 May 2019 18:44:05 +0000 [thread overview]
Message-ID: <20190521184405.41068-1-yinan.wang@intel.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 3412 bytes --]
From: Wang Yinan <yinan.wang@intel.com>
Signed-off-by: Wang Yinan <yinan.wang@intel.com>
---
...pvp_virtio_user_2M_hugepages_test_plan.rst | 60 +++++++++++++++++++
1 file changed, 60 insertions(+)
create mode 100644 test_plans/pvp_virtio_user_2M_hugepages_test_plan.rst
diff --git a/test_plans/pvp_virtio_user_2M_hugepages_test_plan.rst b/test_plans/pvp_virtio_user_2M_hugepages_test_plan.rst
new file mode 100644
index 0000000..8a8355f
--- /dev/null
+++ b/test_plans/pvp_virtio_user_2M_hugepages_test_plan.rst
@@ -0,0 +1,60 @@
+.. 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/virtio-user pvp with 2M hugepage test plan
+================================================
+
+Description
+===========
+
+Before 18.05, virtio-user can only work 1G hugepage. After 18.05, more hugepage pages can be represented by single fd (file descriptor)file, so virtio-user can work with 2M hugepage now. The key parameter is "--single-file-segments" when launch virtio-user.
+
+Test Case1: Basic test for virtio-user 2M hugepage
+===================================================
+
+1. Before the test, plese make sure only 2M hugepage are mounted in host.
+
+2. Bind one port to igb_uio, launch vhost::
+
+ ./testpmd -l 3-4 -n 4 --socket-mem 1024,1024 --file-prefix=vhost \
+ --vdev 'net_vhost0,iface=/tmp/sock0,queues=1' -- -i
+
+3. Launch virtio-user with 2M hugepage::
+
+ ./testpmd -l 5-6 -n 4 --no-pci --socket-mem 1024,1024 --single-file-segments --file-prefix=virtio-user \
+ --vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,queues=1 -- -i
+
+
+3. Send packet with packet generator with different packet size,includes [64, 128, 256, 512, 1024, 1518], check the throughput with below command::
+
+ testpmd>show port stats all
\ No newline at end of file
--
2.17.1
next reply other threads:[~2019-05-22 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 18:44 Yinan [this message]
2019-05-22 6:02 ` Li, WenjieX A
2019-05-29 2:21 ` 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=20190521184405.41068-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).