From: lingwei <weix.ling@intel.com>
To: dts@dpdk.org
Cc: lingwei <weix.ling@intel.com>
Subject: [dts] [dts 3/5] test_plans/vmdq_test_plan:update test plan to sync with testcase
Date: Mon, 7 Sep 2020 15:35:30 +0000 [thread overview]
Message-ID: <20200907153532.37857-4-weix.ling@intel.com> (raw)
In-Reply-To: <20200907153532.37857-1-weix.ling@intel.com>
Signed-off-by: lingwei <weix.ling@intel.com>
---
test_plans/vmdq_test_plan.rst | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/test_plans/vmdq_test_plan.rst b/test_plans/vmdq_test_plan.rst
index 1f19e6f..55ea0d7 100644
--- a/test_plans/vmdq_test_plan.rst
+++ b/test_plans/vmdq_test_plan.rst
@@ -66,7 +66,10 @@ Prerequisites
to the pools numbers(e.g: for FVL spirit, it's 63, inclusive) as well as the MAC address from
52:54:00:12:[port_index]:00 to 52:54:00:12:[port_index]:3e and the VLAN user priority field increments from 0 to 7
(inclusive) for each VLAN ID. In our case port_index = 0 or 1.
-
+-Case config::
+ If test max queues per port 1024, need to set the "CONFIG_RTE_MAX_QUEUES_PER_PORT=1024" in ./config/common_base,
+ and need to set the "define MAX_QUEUES 1024" in ./examples/vmdq/main.c and re-build DPDK.
+ Note: different NIC, the MAX_QUEUES is different, eg: Fortville is 1024.
Test Case: Measure VMDQ pools queues
------------------------------------
--
2.17.1
next prev parent reply other threads:[~2020-09-07 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 15:35 [dts] [PATCH V2 0/5] update " lingwei
2020-09-07 15:35 ` [dts] [dts 1/5] test_plans/nic_single_core_perf_test_plan:update " lingwei
2020-09-07 15:35 ` [dts] [dts 2/5] test_plans/pmd_test_plan:update " lingwei
2020-09-07 15:35 ` lingwei [this message]
2020-09-07 15:35 ` [dts] [dts 4/5] test_plans/ptpclient_test_plan:update " lingwei
2020-09-07 15:35 ` [dts] [dts 5/5] test_plans/vf_l3fwd_test_plan:update " lingwei
2020-09-07 8:21 ` Ma, LihongX
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=20200907153532.37857-4-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).