From: "Zhou, Jun" <junx.w.zhou@intel.com>
To: dts@dpdk.org
Cc: Zhou jun <junx.w.zhou@intel.com>
Subject: [dts] [PATCH V1] update test_plan to synchronize with code
Date: Thu, 3 Sep 2020 08:54:11 +0000 [thread overview]
Message-ID: <20200903085411.5648-1-junx.w.zhou@intel.com> (raw)
From: Zhou jun <junx.w.zhou@intel.com>
modify distributor/external_mempool_handler/vf_jumboframe testplan to synchronize with code
Signed-off-by: Zhou jun <junx.w.zhou@intel.com>
---
test_plans/distributor_test_plan.rst | 4 ++++
test_plans/external_mempool_handler_test_plan.rst | 25 ++++++++++++++++++-----
test_plans/vf_jumboframe_test_plan.rst | 4 ++++
3 files changed, 28 insertions(+), 5 deletions(-)
diff --git a/test_plans/distributor_test_plan.rst b/test_plans/distributor_test_plan.rst
index 7af496a..bc27985 100644
--- a/test_plans/distributor_test_plan.rst
+++ b/test_plans/distributor_test_plan.rst
@@ -71,6 +71,10 @@ Verify burst distributor API cost much less cycles then normal version
Test case: Distribute with maximum workers
==========================================
+In order to make more queue as worker, let a core receive and a core send::
+
+ sed -i -e 's/.*txRings = .*/\\tconst uint16_t rxRings = 1, txRings = 1;/' ./examples/distributor/main.c
+
Start distributor sample with 63(0xeffffffffffffffff0) workers
Send several packets with ip address increasing
diff --git a/test_plans/external_mempool_handler_test_plan.rst b/test_plans/external_mempool_handler_test_plan.rst
index be53272..09ed4ca 100644
--- a/test_plans/external_mempool_handler_test_plan.rst
+++ b/test_plans/external_mempool_handler_test_plan.rst
@@ -42,7 +42,10 @@ systems and software based memory allocators to be used with DPDK.
Test Case 1: Multiple producers and multiple consumers
======================================================
-1. Change default mempool handler operations to "ring_mp_mc"
+1. Change default mempool handler operations to "ring_mp_mc"::
+
+ sed -i 's/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=.*$/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=\"ring_mp_mc\"/' ./config/common_base
+
2. Start test app and verify mempool autotest passed::
test -n 4 -c f
@@ -60,7 +63,10 @@ Test Case 1: Multiple producers and multiple consumers
Test Case 2: Single producer and Single consumer
================================================
-1. Change default mempool operation to "ring_sp_sc"
+1. Change default mempool operation to "ring_sp_sc"::
+
+ sed -i 's/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=.*$/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=\"ring_sp_sc\"/' ./config/common_base
+
2. Start test app and verify mempool autotest passed::
test -n 4 -c f
@@ -78,7 +84,10 @@ Test Case 2: Single producer and Single consumer
Test Case 3: Single producer and Multiple consumers
===================================================
-1. Change default mempool operation to "ring_sp_mc"
+1. Change default mempool operation to "ring_sp_mc"::
+
+ sed -i 's/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=.*$/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=\"ring_sp_mc\"/' ./config/common_base
+
2. Start test app and verify mempool autotest passed::
test -n 4 -c f
@@ -96,7 +105,10 @@ Test Case 3: Single producer and Multiple consumers
Test Case 4: Multiple producers and single consumer
===================================================
-1. Change default mempool operation to "ring_mp_sc"
+1. Change default mempool operation to "ring_mp_sc"::
+
+ sed -i 's/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=.*$/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=\"ring_mp_sc\"/' ./config/common_base
+
2. Start test app and verify mempool autotest passed::
test -n 4 -c f
@@ -114,7 +126,10 @@ Test Case 4: Multiple producers and single consumer
Test Case 4: Stack mempool handler
==================================
-1. Change default mempool operation to "stack"
+1. Change default mempool operation to "stack"::
+
+ sed -i 's/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=.*$/CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS=\"stack\"/' ./config/common_base
+
2. Start test app and verify mempool autotest passed::
test -n 4 -c f
diff --git a/test_plans/vf_jumboframe_test_plan.rst b/test_plans/vf_jumboframe_test_plan.rst
index 2f4cae3..6f8f8b6 100644
--- a/test_plans/vf_jumboframe_test_plan.rst
+++ b/test_plans/vf_jumboframe_test_plan.rst
@@ -107,6 +107,10 @@ Testing the support of Jumbo Frames in Poll Mode Drivers consists in
configuring the maximum packet length with a value greater than 1518, and in
sending to the test machine packets with the following lengths (CRC included):
+when driver is ixgbe, turn on the jumbo_frame switch::
+
+ sed -i -e 's/.jumbo_frame = .*$/.jumbo_frame = 1,/g' app/test-pmd/testpmd.c
+
#. packet length = 1518 - 1
#. packet length = 1518
--
1.8.3.1
next reply other threads:[~2020-09-03 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 8:54 Zhou, Jun [this message]
2020-09-03 10:24 ` Zhou, JunX W
2020-09-15 2:52 ` Tu, Lijuan
-- strict thread matches above, loose matches on Subject: below --
2020-09-03 8:52 Zhou, Jun
2020-09-03 8:32 Zhou, Jun
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=20200903085411.5648-1-junx.w.zhou@intel.com \
--to=junx.w.zhou@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).