[dts][PATCH V3 2/5] test_plans/*: modify test plan to adapt meson build
Yu Jiang
yux.jiang at intel.com
Thu Feb 24 14:46:32 CET 2022
test_plans/*: modify test plan to adapt meson build,
including linux_modules,metrics,multicast,shutdown_api
Signed-off-by: Yu Jiang <yux.jiang at intel.com>
---
test_plans/linux_modules_test_plan.rst | 2 --
test_plans/metrics_test_plan.rst | 10 +++---
test_plans/multicast_test_plan.rst | 44 +++++++++++++-------------
test_plans/shutdown_api_test_plan.rst | 2 +-
4 files changed, 28 insertions(+), 30 deletions(-)
diff --git a/test_plans/linux_modules_test_plan.rst b/test_plans/linux_modules_test_plan.rst
index e8d41996..35b120fc 100644
--- a/test_plans/linux_modules_test_plan.rst
+++ b/test_plans/linux_modules_test_plan.rst
@@ -148,12 +148,10 @@ application.
Compile the application ::
- make: # cd $RTE_SDK/examples/helloworld && make
meson: meson configure -Dexamples=helloworld <build_target>;ninja -C <build_target>
Run the application ::
- make: $ $RTE_SDK/examples/helloworld/build/helloworld-shared --in-memory
meson: $ ./<build_target>/examples/dpdk-helloworld --in-memory
Check for any error states or reported errors.
diff --git a/test_plans/metrics_test_plan.rst b/test_plans/metrics_test_plan.rst
index 22c31f34..2ba3617d 100644
--- a/test_plans/metrics_test_plan.rst
+++ b/test_plans/metrics_test_plan.rst
@@ -35,11 +35,11 @@ metrics
=======
The Metrics implements a mechanism by which *producers* can publish numeric
-information for later querying by *consumers*. Here dpdk-procinfo process is the
+information for later querying by *consumers*. Here dpdk-proc-info process is the
*consumers*. ``latency stats`` and ``bit rate`` are the two implements based
on metrics lib.
-The dpdk-procinfo process use new command line option "--metrics" to display
+The dpdk-proc-info process use new command line option "--metrics" to display
metrics statistics.
Functionality:
@@ -178,7 +178,7 @@ Test Case : test latency stats
#. run dpdk-proc to get latency stats data, query data at a average interval and
get 5 times data::
- ./x86_64-native-linuxapp-gcc/app/dpdk-procinfo -- --metrics
+ ./x86_64-native-linuxapp-gcc/app/dpdk-proc-info -- --metrics
#. latency stats has no reference standard data, only check non-zero and logic reasonable value.
@@ -203,7 +203,7 @@ Test Case : test bit rate
#. run dpdk-proc to get latency stats data, query data at a average interval and
get 5 times data::
- ./x86_64-native-linuxapp-gcc/app/dpdk-procinfo -- --metrics
+ ./x86_64-native-linuxapp-gcc/app/dpdk-proc-info -- --metrics
#. Compare dpdk statistics data with packet generator statistics data.
@@ -228,7 +228,7 @@ Test Case : test bit rate peak value
#. run dpdk-proc to get latency stats data, query data at a average interval and
get 5 times data::
- ./x86_64-native-linuxapp-gcc/app/dpdk-procinfo -- --metrics
+ ./x86_64-native-linuxapp-gcc/app/dpdk-proc-info -- --metrics
#. decline packet generator rate percent from 100%/80%/60%/20%, loop step 5/6.
diff --git a/test_plans/multicast_test_plan.rst b/test_plans/multicast_test_plan.rst
index 87b3dc78..11d84347 100644
--- a/test_plans/multicast_test_plan.rst
+++ b/test_plans/multicast_test_plan.rst
@@ -240,7 +240,7 @@ Here is a table which shows the requirements for which TG flows should arrive fr
Assuming that ports ``0`` and ``2`` are connected to a traffic generator,
launch the ``ipv4_multicast`` with the following arguments::
- ./examples/ipv4_multicast/build/ipv4_multicast -c 0x2 -n 1 -- -p 0x5 -q 2
+ ./<build_target>/examples/dpdk-ipv4_multicast -c 0x2 -n 1 -- -p 0x5 -q 2
If the app run successfully, it will be the same as the shown in the terminal. ::
@@ -302,24 +302,24 @@ used during test execution.
|
-+-----+-------------------------------------------------------+
-| # | Command Line |
-+-----+-------------------------------------------------------+
-|1 |./ipv4_multicast -c 0x40 -n 3 -- -p PORTMASK -q 2 |
-+-----+-------------------------------------------------------+
-|2 |./ipv4_multicast -c 0x400040 -n 3 -- -p PORTMASK -q 1 |
-+-----+-------------------------------------------------------+
-|3 |./ipv4_multicast -c 0x30 -n 3 -- -p PORTMASK -q 1 |
-+-----+-------------------------------------------------------+
-|4 |./ipv4_multicast -c 0x40 -n 3 -- -p PORTMASK -q 2 |
-+-----+-------------------------------------------------------+
-|5 |./ipv4_multicast -c 0x400040 -n 3 -- -p PORTMASK -q 1 |
-+-----+-------------------------------------------------------+
-|6 |./ipv4_multicast -c 0x30 -n 3 -- -p PORTMASK -q 1 |
-+-----+-------------------------------------------------------+
-|7 |./ipv4_multicast -c 0x40 -n 3 -- -p PORTMASK -q 2 |
-+-----+-------------------------------------------------------+
-|8 |./ipv4_multicast -c 0x400040 -n 3 -- -p PORTMASK -q 1 |
-+-----+-------------------------------------------------------+
-|9 |./ipv4_multicast -c 0x30 -n 3 -- -p PORTMASK -q 1 |
-+-----+-------------------------------------------------------+
++-----+------------------------------------------------------------------------------------+
+| # | Command Line |
++-----+------------------------------------------------------------------------------------+
+|1 |./<build_target>/examples/dpdk-ipv4_multicast -c 0x40 -n 3 -- -p PORTMASK -q 2 |
++-----+------------------------------------------------------------------------------------+
+|2 |./<build_target>/examples/dpdk-ipv4_multicast -c 0x400040 -n 3 -- -p PORTMASK -q 1 |
++-----+------------------------------------------------------------------------------------+
+|3 |./<build_target>/examples/dpdk-ipv4_multicast -c 0x30 -n 3 -- -p PORTMASK -q 1 |
++-----+------------------------------------------------------------------------------------+
+|4 |./<build_target>/examples/dpdk-ipv4_multicast -c 0x40 -n 3 -- -p PORTMASK -q 2 |
++-----+------------------------------------------------------------------------------------+
+|5 |./<build_target>/examples/dpdk-ipv4_multicast -c 0x400040 -n 3 -- -p PORTMASK -q 1 |
++-----+------------------------------------------------------------------------------------+
+|6 |./<build_target>/examples/dpdk-ipv4_multicast -c 0x30 -n 3 -- -p PORTMASK -q 1 |
++-----+------------------------------------------------------------------------------------+
+|7 |./<build_target>/examples/dpdk-ipv4_multicast -c 0x40 -n 3 -- -p PORTMASK -q 2 |
++-----+------------------------------------------------------------------------------------+
+|8 |./<build_target>/examples/dpdk-ipv4_multicast -c 0x400040 -n 3 -- -p PORTMASK -q 1 |
++-----+------------------------------------------------------------------------------------+
+|9 |./<build_target>/examples/dpdk-ipv4_multicast -c 0x30 -n 3 -- -p PORTMASK -q 1 |
++-----+------------------------------------------------------------------------------------+
diff --git a/test_plans/shutdown_api_test_plan.rst b/test_plans/shutdown_api_test_plan.rst
index 5a44b78d..a22481a6 100644
--- a/test_plans/shutdown_api_test_plan.rst
+++ b/test_plans/shutdown_api_test_plan.rst
@@ -179,7 +179,7 @@ This case support all the nic with driver i40e and ixgbe.
bind a VF to DPDK::
./usertools/dpdk-devbind.py -b igb_uio 1b:02.0
3. launch testpmd with cmd::
- ./x86_64-native-linuxapp-gcc/app/testpmd -l 0-3 -n 4 --file-prefix=minjq -- -i
+ ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 0-3 -n 4 --file-prefix=minjq -- -i
4. Run ``port stop all`` to stop all ports.
5. Run ``port config all speed SPEED duplex HALF/FULL`` to select the new config for the link.
6. Run ``port start all`` to restart all ports.
--
2.25.1
More information about the dts
mailing list