From: lingwei <weix.ling@intel.com>
To: dts@dpdk.org
Cc: lingwei <weix.ling@intel.com>
Subject: [dts] [dts 4/5] test_plans/vf_l3fwd_test_plan:update test plan to sync with testcase
Date: Mon, 7 Sep 2020 16:49:28 +0000 [thread overview]
Message-ID: <20200907164929.51247-5-weix.ling@intel.com> (raw)
In-Reply-To: <20200907164929.51247-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..6d816dd 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 2048"
+ 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
next prev parent reply other threads:[~2020-09-07 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 16:49 [dts] [PATCH V3 0/5] update " lingwei
2020-09-07 16:49 ` [dts] [dts 1/5] test_plans/nic_single_core_perf_test_plan:update " lingwei
2020-09-07 16:49 ` [dts] [dts 2/5] test_plans/pmd_test_plan:update " lingwei
2020-09-07 16:49 ` [dts] [dts 3/5] test_plans/ptpclient_test_plan:update " lingwei
2020-09-07 16:49 ` lingwei [this message]
2020-09-07 16:49 ` [dts] [dts 5/5] test_plans/vmdq_test_plan:update " lingwei
2020-09-08 3:31 ` [dts] [PATCH V3 0/5] update " Ma, LihongX
2020-09-10 5:12 ` 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=20200907164929.51247-5-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).