test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yu Jiang <yux.jiang@intel.com>
To: lijuan.tu@intel.com, dts@dpdk.org
Cc: Yu Jiang <yux.jiang@intel.com>
Subject: [dts][PATCH V1 3/3] test_plans/external_mempool_handler: modify test plan to adapt meson build
Date: Thu, 14 Apr 2022 14:05:49 +0000	[thread overview]
Message-ID: <20220414140549.1579777-4-yux.jiang@intel.com> (raw)
In-Reply-To: <20220414140549.1579777-1-yux.jiang@intel.com>

test_plans/external_mempool_handler: modify test plan to adapt meson build

Signed-off-by: Yu Jiang <yux.jiang@intel.com>
---
 .../external_mempool_handler_test_plan.rst    | 32 +++++++++----------
 1 file changed, 16 insertions(+), 16 deletions(-)

diff --git a/test_plans/external_mempool_handler_test_plan.rst b/test_plans/external_mempool_handler_test_plan.rst
index c773dc0b..0df16182 100644
--- a/test_plans/external_mempool_handler_test_plan.rst
+++ b/test_plans/external_mempool_handler_test_plan.rst
@@ -42,14 +42,14 @@ systems and software based memory allocators to be used with DPDK.
 Test Case 1: Multiple producers and multiple consumers
 ======================================================
 
-1. Default mempool handler operations is "ring_mp_mc"::
+1. Default mempool handler operations RTE_MBUF_DEFAULT_MEMPOOL_OPS is "ring_mp_mc"::
 
-      cat /root/dpdk/config/rte_config.h |grep MEMPOOL_OPS
-      #define RTE_MBUF_DEFAULT_MEMPOOL_OPS "ring_mp_mc"
+      Launch test app with mempool operation "ring_mp_mc":
+      parameter: --mbuf-pool-ops-name ring_mp_mc
 
 2. Start test app and verify mempool autotest passed::
 
-      ./<build_target>/app/test/dpdk-test -n 4 -c f
+      ./<build_target>/app/test/dpdk-test -n 4 -c f --mbuf-pool-ops-name ring_mp_mc
       RTE>> mempool_autotest
 
 3. Start testpmd with two ports and start forwarding::
@@ -64,13 +64,13 @@ 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. Launch test app with mempool operation "ring_sp_sc"::
 
-      sed -i '$a\#define RTE_MBUF_DEFAULT_MEMPOOL_OPS \"ring_sp_sc\"' config/rte_config.h
+      parameter: --mbuf-pool-ops-name ring_sp_sc
 
 2. Start test app and verify mempool autotest passed::
 
-      ./<build_target>/app/test/dpdk-test -n 4 -c f
+      ./<build_target>/app/test/dpdk-test -n 4 -c f --mbuf-pool-ops-name ring_sp_sc
       RTE>> mempool_autotest
 
 3. Start testpmd with two ports and start forwarding::
@@ -85,13 +85,13 @@ 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. Launch test app with mempool operation "ring_sp_mc"::
 
-      sed -i '$a\#define RTE_MBUF_DEFAULT_MEMPOOL_OPS \"ring_sp_mc\"' config/rte_config.h
+      parameter: --mbuf-pool-ops-name ring_sp_mc
 
 2. Start test app and verify mempool autotest passed::
 
-      ./<build_target>/app/test/dpdk-test -n 4 -c f
+      ./<build_target>/app/test/dpdk-test -n 4 -c f --mbuf-pool-ops-name ring_sp_mc
       RTE>> mempool_autotest
 
 3. Start testpmd with two ports and start forwarding::
@@ -106,13 +106,13 @@ 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. Launch test app with mempool operation "ring_mp_sc"::
 
-      sed -i '$a\#define RTE_MBUF_DEFAULT_MEMPOOL_OPS \"ring_mp_sc\"' config/rte_config.h
+      parameter: --mbuf-pool-ops-name ring_mp_sc
 
 2. Start test app and verify mempool autotest passed::
 
-      ./<build_target>/app/test/dpdk-test -n 4 -c f
+      ./<build_target>/app/test/dpdk-test -n 4 -c f --mbuf-pool-ops-name ring_mp_sc
       RTE>> mempool_autotest
 
 3. Start testpmd with two ports and start forwarding::
@@ -127,13 +127,13 @@ Test Case 4: Multiple producers and single consumer
 Test Case 4: Stack mempool handler
 ==================================
 
-1. Change default mempool operation to "stack"::
+1. Launch test app with mempool operation "stack"::
 
-      sed -i '$a\#define RTE_MBUF_DEFAULT_MEMPOOL_OPS \"stack\"' config/rte_config.h
+      parameter: --mbuf-pool-ops-name stack
 
 2. Start test app and verify mempool autotest passed::
 
-      ./<build_target>/app/test/dpdk-test -n 4 -c f
+      ./<build_target>/app/test/dpdk-test -n 4 -c f --mbuf-pool-ops-name stack
       RTE>> mempool_autotest
 
 3. Start testpmd with two ports and start forwarding::
-- 
2.25.1


      parent reply	other threads:[~2022-04-14  6:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 14:05 [dts][PATCH V1 0/3] test_plans/*: " Yu Jiang
2022-04-14 14:05 ` [dts][PATCH V1 1/3] test_plans/vf_interrupt_pmd&sriov_kvm: " Yu Jiang
2022-04-20  3:34   ` lijuan.tu
2022-04-14 14:05 ` [dts][PATCH V1 2/3] test_plans/l2fwd_cryptodev_func&inline_ipsec: " Yu Jiang
2022-04-14 14:05 ` Yu Jiang [this message]

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=20220414140549.1579777-4-yux.jiang@intel.com \
    --to=yux.jiang@intel.com \
    --cc=dts@dpdk.org \
    --cc=lijuan.tu@intel.com \
    /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).