test suite reviews and discussions
 help / color / mirror / Atom feed
From: wang fei <feix.y.wang@intel.com>
To: dts@dpdk.org
Cc: wang fei <feix.y.wang@intel.com>
Subject: [dts] [DTS][Patch V1 2/2] test plan for vf_perf test suite
Date: Mon, 14 May 2018 12:24:33 +0800	[thread overview]
Message-ID: <1526271873-22766-1-git-send-email-feix.y.wang@intel.com> (raw)

Put in test plan for test suite of vf_perf.

Signed-off-by: wang fei <feix.y.wang@intel.com>
---
 test_plans/vf_perf_test_plan.rst | 103 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 103 insertions(+)
 create mode 100644 test_plans/vf_perf_test_plan.rst

diff --git a/test_plans/vf_perf_test_plan.rst b/test_plans/vf_perf_test_plan.rst
new file mode 100644
index 0000000..fd079a5
--- /dev/null
+++ b/test_plans/vf_perf_test_plan.rst
@@ -0,0 +1,103 @@
+.. 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.
+
+
+====================
+VF performance test
+===================
+
+This document provides benchmark test for NIC VFs which are created from
+kernel PFs or DPDK PFs.
+
+
+Prerequisites
+==============
+
+For FVL40G, FVL25G, use 2 ports from two NICs, 2 core 2 queues per port.
+For FVL4x10G NIC, use 4 ports from 1 NIC, 1 core 1 queues per port.
+For NNT NIC, use 2 ports from 2 NIC, 1 core 1 queues per port.
+
+
+
+Test Case 1: Measure performace with kernel PF & dpdk VF
+========================================================
+
+1. Two (or four for FVL4x10G) NIC PF ports, using kernel driver, create 1 VF from each PF.
+
+2. Bind the two created VFs to dpdk driver and start dpdk l3fwd.
+
+3. send packet stream from 64bytes to 1518bytes with ixia traffic generator, 
+got output result, the format should be as below, with figures given in Mpps:
+
++-------+------+--------+-----------+
+| Frame | mode | Mpps   | %linerate |
++=======+======+========+===========+
+| 64    | lpm  |        |           |
++-------+------+--------+-----------+
+| 128   | lpm  |        |           |
++-------+------+--------+-----------+
+| 256   | lpm  |        |           |
++-------+------+--------+-----------+
+| 512   | lpm  |        |           |
++-------+------+--------+-----------+
+| 1024  | lpm  |        |           |
++-------+------+--------+-----------+
+| 1518  | lpm  |        |           |
++-------+------+--------+-----------+
+
+
+Test Case 2: Measure performace with dpdk PF & dpdk VF
+======================================================
+
+1. Two (or four for FVL4x10G) NIC PF ports, binding to igb_uio driver, then create 1 VF from each PF.
+
+2. Bind the two created VFs to dpdk driver and start dpdk l3fwd.
+
+3. send packet stream from 64bytes to 1518bytes with ixia traffic generator, 
+got output result, the format should be as below, with figures given in Mpps:
+
++-------+------+--------+-----------+
+| Frame | mode | Mpps   | %linerate |
++=======+======+========+===========+
+| 64    | lpm  |        |           |
++-------+------+--------+-----------+
+| 128   | lpm  |        |           |
++-------+------+--------+-----------+
+| 256   | lpm  |        |           |
++-------+------+--------+-----------+
+| 512   | lpm  |        |           |
++-------+------+--------+-----------+
+| 1024  | lpm  |        |           |
++-------+------+--------+-----------+
+| 1518  | lpm  |        |           |
++-------+------+--------+-----------+
+
-- 
2.7.4

                 reply	other threads:[~2018-05-14  1:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1526271873-22766-1-git-send-email-feix.y.wang@intel.com \
    --to=feix.y.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).