test suite reviews and discussions
 help / color / mirror / Atom feed
From: lingwei <weix.ling@intel.com>
To: dts@dpdk.org
Cc: lingwei <weix.ling@intel.com>
Subject: [dts] [dts 6/6] test_plans/vf_l3fwd_test_plan: update test plan to sync with testcase
Date: Wed,  2 Sep 2020 14:15:00 +0000	[thread overview]
Message-ID: <20200902141500.92740-7-weix.ling@intel.com> (raw)
In-Reply-To: <20200902141500.92740-1-weix.ling@intel.com>

Signed-off-by: lingwei <weix.ling@intel.com>
---
 test_plans/vf_l3fwd_test_plan.rst | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/test_plans/vf_l3fwd_test_plan.rst b/test_plans/vf_l3fwd_test_plan.rst
index 8b51cef..ec0f1cb 100644
--- a/test_plans/vf_l3fwd_test_plan.rst
+++ b/test_plans/vf_l3fwd_test_plan.rst
@@ -82,6 +82,15 @@ Prerequisites
       | NIC-2,Port-1  ---  TG,Port-2 |
       +------------------------------+
 
+* Case config:
+    For test vf_l3fwd perf, need to set "define RTE_TEST_RX_DESC_DEFAULT 2048" and "define RTE_TEST_TX_DESC_DEFAULT 20480"
+    in ./examples/l3fwd/l3fwd.h and re-build l3fwd.
+  Note:
+    Only FVL need to change code to support iavf, when dpdk use iavf as default vf driver, no need to change code.
+    If test iavf on FVL, need to change "{ RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID, IAVF_DEV_ID_ADAPTIVE_VF) }" to
+    "a { RTE_PCI_DEVICE(IAVF_INTEL_VENDOR_ID, IAVF_DEV_ID_VF) }" in ./drivers/net/iavf/iavf_ethdev.c,
+    and set "I40E_DEV_ID_VF 0x164C" in ./drivers/net/i40e/base/i40e_devids.h and re-build DPDK.
+
 Setup overview
 ==============
 
-- 
2.17.1


  parent reply	other threads:[~2020-09-02  6:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 14:14 [dts] [PATCH V1 0/6] " lingwei
2020-09-02 14:14 ` [dts] [dts 1/6] tests/TestSuite_vmdq_dcb: set dpdk config before build by meson and use api to get app name lingwei
2020-09-02 14:14 ` [dts] [dts 2/6] test_plans/nic_single_core_perf_test_plan: update test plan to sync with testcase lingwei
2020-09-02 14:14 ` [dts] [dts 3/6] test_plans/pmd_test_plan: " lingwei
2020-09-02 14:14 ` [dts] [dts 4/6] test_plans/vmdq_test_plan: " lingwei
2020-09-02 14:14 ` [dts] [dts 5/6] test_plans/ptpclient_test_plan: " lingwei
2020-09-02 14:15 ` lingwei [this message]
2020-09-07  5:19 ` [dts] [PATCH V1 0/6] " Ma, LihongX
2020-09-07  5:52   ` Ling, WeiX

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=20200902141500.92740-7-weix.ling@intel.com \
    --to=weix.ling@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).