test suite reviews and discussions
 help / color / mirror / Atom feed
* [dts][PATCH V1 0/3] test_plans/*: modify test plan to adapt meson build
@ 2022-04-14 14:05 Yu Jiang
  2022-04-14 14:05 ` [dts][PATCH V1 1/3] test_plans/vf_interrupt_pmd&sriov_kvm: " Yu Jiang
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Yu Jiang @ 2022-04-14 14:05 UTC (permalink / raw)
  To: lijuan.tu, dts; +Cc: Yu Jiang

test_plans/*: modify test plan to adapt meson build

Yu Jiang (3):
  test_plans/vf_interrupt_pmd&sriov_kvm: modify test plan to adapt meson
    build
  test_plans/l2fwd_cryptodev_func&inline_ipsec: modify test plan to
    adapt meson build
  test_plans/external_mempool_handler: modify test plan to adapt meson
    build

 .../external_mempool_handler_test_plan.rst    | 32 +++++++++----------
 test_plans/inline_ipsec_test_plan.rst         | 20 ++++++------
 test_plans/l2fwd_cryptodev_func_test_plan.rst |  2 +-
 test_plans/sriov_kvm_test_plan.rst            | 28 ++++++++--------
 test_plans/vf_interrupt_pmd_test_plan.rst     |  2 +-
 5 files changed, 42 insertions(+), 42 deletions(-)

-- 
2.25.1


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [dts][PATCH V1 1/3] test_plans/vf_interrupt_pmd&sriov_kvm: modify test plan to adapt meson build
  2022-04-14 14:05 [dts][PATCH V1 0/3] test_plans/*: modify test plan to adapt meson build Yu Jiang
@ 2022-04-14 14:05 ` 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 ` [dts][PATCH V1 3/3] test_plans/external_mempool_handler: " Yu Jiang
  2 siblings, 1 reply; 5+ messages in thread
From: Yu Jiang @ 2022-04-14 14:05 UTC (permalink / raw)
  To: lijuan.tu, dts; +Cc: Yu Jiang

test_plans/vf_interrupt_pmd&sriov_kvm: modify test plan to adapt meson build

Signed-off-by: Yu Jiang <yux.jiang@intel.com>
---
 test_plans/sriov_kvm_test_plan.rst        | 28 +++++++++++------------
 test_plans/vf_interrupt_pmd_test_plan.rst |  2 +-
 2 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/test_plans/sriov_kvm_test_plan.rst b/test_plans/sriov_kvm_test_plan.rst
index ff3ecd07..1adc4dc2 100644
--- a/test_plans/sriov_kvm_test_plan.rst
+++ b/test_plans/sriov_kvm_test_plan.rst
@@ -57,7 +57,7 @@ used to generate 2VFs and make them in pci-stub modes.::
 
 Start PF driver on the Host and skip the VFs.::
 
-    ./x86_64-default-linuxapp-gcc/app/testpmd -c f \
+    ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f \
        -n 4 -b 0000:08:10.0  -b 0000:08:10.2 --  -i
 
 For VM0 start up command, you can refer to below command.::
@@ -95,11 +95,11 @@ If you want to run all common 2VM cases, please run testpmd on VM0 and VM1 and
 start traffic forward on the VM hosts. Some specific prerequisites need to be
 set up in each case::
 
-    VF0 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  -i
+    VF0 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  -i
     VF0 testpmd-> set fwd rxonly
     VF0 testpmd-> start
 
-    VF1 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  -i
+    VF1 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  -i
     VF1 testpmd-> set fwd mac
     VF1 testpmd-> start
 
@@ -109,12 +109,12 @@ Test Case: InterVM communication test on 2VMs
 Set the VF0 destination mac address to VF1 mac address, packets send from VF0
 will be forwarded to VF1 and then send out::
 
-    VF1 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  -i
+    VF1 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  -i
     VF1 testpmd-> show port info 0
     VF1 testpmd-> set fwd mac
     VF1 testpmd-> start
 
-    VF0 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  --eth-peer=0,"VF1 mac" -i
+    VF0 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  --eth-peer=0,"VF1 mac" -i
     VF0 testpmd-> set fwd mac
     VF0 testpmd-> start
 
@@ -255,16 +255,16 @@ driver will has been already attached to VMs::
 
     On PF ./tools/pci_unbind.py --bind=igb_uio 0000:08:00.0
     echo 4 > /sys/bus/pci/devices/0000\:08\:00.0/max_vfs
-    ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 -b 0000:08:10.0 -b 0000:08:10.2 -b 0000:08:10.4 -b 0000:08:10.6 --  -i
+    ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 -b 0000:08:10.0 -b 0000:08:10.2 -b 0000:08:10.4 -b 0000:08:10.6 --  -i
 
 If you want to run all common 4VM cases, please run testpmd on VM0, VM1, VM2
 and VM3 and start traffic forward on the VM hosts. Some specific prerequisites
 are set up in each case::
 
-    VF0 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  -i
-    VF1 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  -i
-    VF2 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  -i
-    VF3 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  -i
+    VF0 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  -i
+    VF1 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  -i
+    VF2 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  -i
+    VF3 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  -i
 
 Test Case: Scaling InterVM communication on 4VFs
 ==================================================
@@ -272,21 +272,21 @@ Test Case: Scaling InterVM communication on 4VFs
 Set the VF0 destination mac address to VF1 mac address, packets send from VF0
 will be forwarded to VF1 and then send out. Similar for VF2 and VF3::
 
-    VF1 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  -i
+    VF1 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  -i
     VF1 testpmd-> show port info 0
     VF1 testpmd-> set fwd mac
     VF1 testpmd-> start
 
-    VF0 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  --eth-peer=0,"VF1 mac" -i
+    VF0 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  --eth-peer=0,"VF1 mac" -i
     VF0 testpmd-> set fwd mac
     VF0 testpmd-> start
 
-    VF3 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  -i
+    VF3 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  -i
     VF3 testpmd-> show port info 0
     VF3 testpmd-> set fwd mac
     VF3 testpmd-> start
 
-    VF2 ./x86_64-default-linuxapp-gcc/app/testpmd -c f -n 4 --  --eth-peer=0,"VF3 mac" -i
+    VF2 ./x86_64-default-linuxapp-gcc/app/dpdk-testpmd -c f -n 4 --  --eth-peer=0,"VF3 mac" -i
     VF2 testpmd-> set fwd mac
     VF2 testpmd-> start
 
diff --git a/test_plans/vf_interrupt_pmd_test_plan.rst b/test_plans/vf_interrupt_pmd_test_plan.rst
index 1988b43d..ac49c5ed 100644
--- a/test_plans/vf_interrupt_pmd_test_plan.rst
+++ b/test_plans/vf_interrupt_pmd_test_plan.rst
@@ -246,7 +246,7 @@ Test Case6: VF multi-queue interrupt in VM with vfio-pci on i40e
 
 4.Start l3fwd-power in VM::
 
-    ./build/l3fwd-power -l 0-3 -n 4 -m 2048 -- -P -p 0x1 --config="(0,0,0),(0,1,1),(0,2,2),(0,3,3)"
+    ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 0-3 -n 4 -m 2048 -- -P -p 0x1 --config="(0,0,0),(0,1,1),(0,2,2),(0,3,3)"
 
 5. Send UDP packets with random ip and dest mac = vf mac addr::
 
-- 
2.25.1


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [dts][PATCH V1 2/3] test_plans/l2fwd_cryptodev_func&inline_ipsec: modify test plan to adapt meson build
  2022-04-14 14:05 [dts][PATCH V1 0/3] test_plans/*: modify test plan to adapt meson build Yu Jiang
  2022-04-14 14:05 ` [dts][PATCH V1 1/3] test_plans/vf_interrupt_pmd&sriov_kvm: " Yu Jiang
@ 2022-04-14 14:05 ` Yu Jiang
  2022-04-14 14:05 ` [dts][PATCH V1 3/3] test_plans/external_mempool_handler: " Yu Jiang
  2 siblings, 0 replies; 5+ messages in thread
From: Yu Jiang @ 2022-04-14 14:05 UTC (permalink / raw)
  To: lijuan.tu, dts; +Cc: Yu Jiang

test_plans/l2fwd_cryptodev_func&inline_ipsec: modify test plan to adapt meson build

Signed-off-by: Yu Jiang <yux.jiang@intel.com>
---
 test_plans/inline_ipsec_test_plan.rst         | 20 +++++++++----------
 test_plans/l2fwd_cryptodev_func_test_plan.rst |  2 +-
 2 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/test_plans/inline_ipsec_test_plan.rst b/test_plans/inline_ipsec_test_plan.rst
index f3b0a8cc..0b4e45a1 100644
--- a/test_plans/inline_ipsec_test_plan.rst
+++ b/test_plans/inline_ipsec_test_plan.rst
@@ -145,7 +145,7 @@ Test Case: IPSec Encryption
 ===========================
 Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
 
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
 	"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 
 	0x2 --config="(0,0,20),(1,0,21)" -f ./enc.cfg
 
@@ -195,7 +195,7 @@ Test Case: IPSec Encryption with Jumboframe
 ===========================================
 Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
 
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
 	"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 
 	0x2 --config="(0,0,20),(1,0,21)" -f ./enc.cfg
 
@@ -215,7 +215,7 @@ Check burst esp packets can't be received from unprotected port.
 
 Set jumbo frames size as 9000, start it with port 1 assigned to unprotected mode::
 
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
 	"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 
 	0x2 -j 9000 --config="(0,0,20),(1,0,21)" -f ./enc.cfg
 
@@ -240,7 +240,7 @@ Create configuration file with multiple SP/SA/RT rules for different ip address.
 
 Start ipsec-secgw with two queues enabled on each port and port 1 assigned to unprotected mode::
 
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
 	"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 
 	0x2 --config="(0,0,20),(0,1,20),(1,0,21),(1,1,21)" -f ./enc_rss.cfg
 
@@ -260,7 +260,7 @@ Test Case: IPSec Decryption
 ===========================
 Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
 
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
 	"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 
 	0x2 --config="(0,0,20),(1,0,21)" -f ./dec.cfg
 
@@ -276,7 +276,7 @@ Test Case: IPSec Decryption with wrong key
 ==========================================
 Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
 
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
 	"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 
 	0x2 --config="(0,0,20),(1,0,21)" -f ./dec.cfg
 
@@ -296,7 +296,7 @@ IPsec application will produce error "IPSEC_ESP: failed crypto op".
 Test Case: IPSec Decryption with Jumboframe
 ===========================================
 Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
 	"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 
 	0x2 --config="(0,0,20),(1,0,21)" -f ./dec.cfg
 
@@ -313,7 +313,7 @@ Check burst(8192) packets which have been decapsulated can't be received from pr
 
 Set jumbo frames size as 9000, start it with port 1 assigned to unprotected mode::
 
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
 	"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 
 	0x2 -j 9000 --config="(0,0,20),(1,0,21)" -f ./dec.cfg
 
@@ -335,7 +335,7 @@ Create configuration file with multiple SA rule for different ip address.
 
 Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
 
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev 
         "crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 
 	0x2 -config="(0,0,20),(0,1,20),(1,0,21),(1,1,21)" -f ./dec_rss.cfg
 
@@ -352,7 +352,7 @@ Test Case: IPSec Encryption/Decryption simultaneously
 =====================================================
 Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
 
-	sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1
+	sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1
         --vdev "crypto_null" --log-level 8 --socket-mem 1024,1 
         -- -p 0xf -P -u 0x2 --config="(0,0,20),(1,0,21)" -f ./enc_dec.cfg
 	
diff --git a/test_plans/l2fwd_cryptodev_func_test_plan.rst b/test_plans/l2fwd_cryptodev_func_test_plan.rst
index 9ace53d0..889b3fd2 100644
--- a/test_plans/l2fwd_cryptodev_func_test_plan.rst
+++ b/test_plans/l2fwd_cryptodev_func_test_plan.rst
@@ -279,7 +279,7 @@ To test CryptoDev API, an example l2fwd-crypto is added into DPDK.
 
 The test commands of l2fwd-crypto is below::
 
-    ./build/l2fwd-crypto [EAL options] -- [-p PORTMASK] [-q NQ] [-s] [-T PERIOD] /
+    ./build/examples/dpdk-l2fwd-crypto [EAL options] -- [-p PORTMASK] [-q NQ] [-s] [-T PERIOD] /
     [--cdev_type HW/SW/ANY] [--chain HASH_CIPHER/CIPHER_HASH/CIPHER_ONLY/HASH_ONLY/AEAD] /
     [--cipher_algo ALGO] [--cipher_op ENCRYPT/DECRYPT] [--cipher_key KEY] /
     [--cipher_key_random_size SIZE] [--cipher_iv IV] [--cipher_iv_random_size SIZE] /
-- 
2.25.1


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [dts][PATCH V1 3/3] test_plans/external_mempool_handler: modify test plan to adapt meson build
  2022-04-14 14:05 [dts][PATCH V1 0/3] test_plans/*: modify test plan to adapt meson build Yu Jiang
  2022-04-14 14:05 ` [dts][PATCH V1 1/3] test_plans/vf_interrupt_pmd&sriov_kvm: " Yu Jiang
  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
  2 siblings, 0 replies; 5+ messages in thread
From: Yu Jiang @ 2022-04-14 14:05 UTC (permalink / raw)
  To: lijuan.tu, dts; +Cc: Yu Jiang

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [dts][PATCH V1 1/3] test_plans/vf_interrupt_pmd&sriov_kvm: modify test plan to adapt meson build
  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
  0 siblings, 0 replies; 5+ messages in thread
From: lijuan.tu @ 2022-04-20  3:34 UTC (permalink / raw)
  To: lijuan.tu, dts, Yu Jiang; +Cc: Yu Jiang

On Thu, 14 Apr 2022 14:05:47 +0000, Yu Jiang <yux.jiang@intel.com> wrote:
> test_plans/vf_interrupt_pmd&sriov_kvm: modify test plan to adapt meson build
> 
> Signed-off-by: Yu Jiang <yux.jiang@intel.com>


Series applied, thanks

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2022-04-20  3:34 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-14 14:05 [dts][PATCH V1 0/3] test_plans/*: modify test plan to adapt meson build 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 ` [dts][PATCH V1 3/3] test_plans/external_mempool_handler: " Yu Jiang

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).