@@ -65,6 +65,7 @@ Setup library path in environment::
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH,<dpdk_2002>
+meson: CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=shared <build_target>;ninja -C <build_target>
Common Test Steps
=================
@@ -75,7 +76,7 @@ application steps are below,
Go into <dpdk_1911> directory, launch application with specific library::
- testpmd -c 0xf -n 4 -d <dpdk_2002> -- -i
+ ./<build_target>/app/dpdk-testpmd -c 0xf -n 4 -d <dpdk_2002> -- -i
Expect the application could launch successfully.
@@ -292,7 +293,7 @@ Build shared libraries, (just enable i40e pmd for testing)::
Run testpmd application refer to Common Test steps with ixgbe pmd NIC.::
- testpmd -c 0xf -n 4 -d <dpdk_2002> -a 18:00.0 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 0xf -n 4 -d <dpdk_2002> -a 18:00.0 -- -i
Test txonly::
@@ -153,7 +153,7 @@ and operations timeout is set to 120s
and enqueue/dequeue burst size is set to 8 and to 32.
Moreover a bbdev (*turbo_sw*) device will be created::
- ./test-bbdev.py -p ../../x86_64-native-linuxapp-icc/app/testbbdev \
+ ./test-bbdev.py -p ../../x86_64-native-linuxapp-icc/app/dpdk-test-bbdev \
-e="--vdev=baseband_turbo_sw" -t 120 -c validation \
-v ./test_vectors/turbo_enc_c1_k40_r0_e1196_rm.data -n 64 -b 8 32
@@ -243,7 +243,7 @@ Test case 8: Turbo encoding and decoding offload and latency
It runs **offload ** and **latency** test for Turbo encode vector file::
- ./test-bbdev.py -p ../../x86_64-native-linuxapp-icc/app/testbbdev \
+ ./test-bbdev.py -p ../../x86_64-native-linuxapp-icc/app/dpdk-test-bbdev \
-e="--vdev=baseband_turbo_sw" -t 120 -c offload latency \
-v ./test_vectors/turbo_enc_c1_k40_r0_e1196_rm.data \
./test_vectors/turbo_dec_c1_k40_r0_e17280_sbd_negllr.data -n 64 -l 16 -b 8 32
@@ -49,7 +49,7 @@ Description: Execute performance test with Atomic_atq type of stage in multi-flo
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=A --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=A --wlcores=23
Parameters::
@@ -76,7 +76,7 @@ Description: Execute performance test with Parallel_atq type of stage in multi-f
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=P --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=P --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -88,7 +88,7 @@ Description: Execute performance test with Ordered_atq type of stage in multi-fl
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=O --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=O --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -100,7 +100,7 @@ Description: Execute performance test with Atomic_queue type of stage in multi-f
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=A --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=A --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -112,7 +112,7 @@ Description: Execute performance test with Parallel_queue type of stage in multi
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=P --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=P --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -124,7 +124,7 @@ Description: Execute performance test with Ordered_queue type of stage in multi-
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=O --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=O --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -136,7 +136,7 @@ Description: Execute performance test with Atomic_atq type of stage in multi-flo
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=A --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=A --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -148,7 +148,7 @@ Description: Execute performance test with Parallel_atq type of stage in multi-f
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=P --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=P --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -160,7 +160,7 @@ Description: Execute performance test with Ordered_atq type of stage in multi-fl
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=O --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=O --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -172,7 +172,7 @@ Description: Execute performance test with Atomic_queue type of stage in multi-f
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=A --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=A --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -184,7 +184,7 @@ Description: Execute performance test with Parallel_queue type of stage in multi
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=P --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=P --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -196,7 +196,7 @@ Description: Execute performance test with Ordered_queue type of stage in multi-
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=O --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=O --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -209,7 +209,7 @@ Description: Execute performance test with Atomic_atq type of stage in multi-flo
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -w device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=A --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -w device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=A --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -221,7 +221,7 @@ Description: Execute performance test with Parallel_atq type of stage in multi-f
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=P --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=P --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -233,7 +233,7 @@ Description: Execute performance test with Ordered_atq type of stage in multi-fl
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=O --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_atq --stlist=O --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -245,7 +245,7 @@ Description: Execute performance test with Atomic_queue type of stage in multi-f
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=A --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=A --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -257,7 +257,7 @@ Description: Execute performance test with Parallel_queue type of stage in multi
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=P --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=P --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -269,7 +269,7 @@ Description: Execute performance test with Ordered_queue type of stage in multi-
1. Run the sample with below command::
- # ./build/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=O --wlcores=23
+ # ./<build_target>/app/dpdk-test-eventdev -l 22-23 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- --prod_type_ethdev --nb_pkts=0 --verbose 2 --test=pipeline_queue --stlist=O --wlcores=23
2. Use Ixia to send huge number of packets(with same 5-tuple and different 5-tuple)
@@ -22,6 +22,13 @@ to the device under test ::
usertools/dpdk-devbind.py --bind=vfio-pci device_bus_id
usertools/dpdk-devbind.py --bind=vfio-pci eventdev_device_bus_id
+Build dpdk and examples=eventdev_pipeline:
+ CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static <build_target>
+ ninja -C <build_target>
+
+ meson configure -Dexamples=eventdev_pipeline <build_target>
+ ninja -C <build_target>
+
Create huge pages
=================
mkdir -p /dev/huge
@@ -51,7 +58,7 @@ Description: Execute performance test with Atomic_atq type of stage in multi-flo
1. Run the sample with below command::
- # ./build/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device_bus_id -- -w 0xc00000 -n=0 --dump
+ # ./<build_target>/examples/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device_bus_id -- -w 0xc00000 -n=0 --dump
Parameters::
@@ -75,7 +82,7 @@ Description: Execute performance test with Parallel_atq type of stage in multi-f
1. Run the sample with below command::
- # ./build/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device_bus_id -- -w 0xc00000 -n=0 -p --dump
+ # ./<build_target>/examples/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device_bus_id -- -w 0xc00000 -n=0 -p --dump
Parameters::
@@ -100,7 +107,7 @@ Description: Execute performance test with Ordered_atq type of stage in multi-fl
1. Run the sample with below command::
- # ./build/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device_bus_id -- -w 0xc00000 -n=0 -o --dump
+ # ./<build_target>/examples/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device_bus_id -- -w 0xc00000 -n=0 -o --dump
Parameters::
@@ -125,7 +132,7 @@ Description: Execute performance test with Atomic_atq type of stage in multi-flo
1. Run the sample with below command::
- # ./build/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- -w 0xc00000 -n=0 --dump
+ # ./<build_target>/examples/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- -w 0xc00000 -n=0 --dump
Parameters::
@@ -149,7 +156,7 @@ Description: Execute performance test with Parallel_atq type of stage in multi-f
1. Run the sample with below command::
- # ./build/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- -w 0xc00000 -n=0 -p --dump
+ # ./<build_target>/examples/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- -w 0xc00000 -n=0 -p --dump
Parameters::
@@ -174,7 +181,7 @@ Description: Execute performance test with Ordered_atq type of stage in multi-fl
1. Run the sample with below command::
- # ./build/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- -w 0xc00000 -n=0 -o --dump
+ # ./<build_target>/examples/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -- -w 0xc00000 -n=0 -o --dump
Parameters::
@@ -199,7 +206,7 @@ Description: Execute performance test with Atomic_atq type of stage in multi-flo
1. Run the sample with below command::
- # ./build/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- -w 0xc00000 -n=0 --dump
+ # ./<build_target>/examples/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- -w 0xc00000 -n=0 --dump
Parameters::
@@ -223,7 +230,7 @@ Description: Execute performance test with Parallel_atq type of stage in multi-f
1. Run the sample with below command::
- # ./build/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- -w 0xc00000 -n=0 -p --dump
+ # ./<build_target>/examples/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- -w 0xc00000 -n=0 -p --dump
Parameters::
@@ -248,7 +255,7 @@ Description: Execute performance test with Ordered_atq type of stage in multi-fl
1. Run the sample with below command::
- # ./build/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- -w 0xc00000 -n=0 -o --dump
+ # ./<build_target>/examples/dpdk-eventdev_pipeline -c 0xe00000 -a eventdev_device_bus_id -a device0_bus_id -a device1_bus_id -a device2_bus_id -a device3_bus_id -- -w 0xc00000 -n=0 -o --dump
Parameters::
@@ -53,7 +53,7 @@ to the device under test::
Assuming that ports are up and working, then launch the ``testpmd`` application
with the following arguments::
- ./build/app/testpmd -- -i --portmask=0x3
+ ./build/app/dpdk-testpmd -- -i --portmask=0x3
Ensure the ```firmware_version.cfg``` file have the correct name and firmware
version.
@@ -114,7 +114,7 @@ To test IPsec, an example ipsec-secgw is added into DPDK.
The test commands of ipsec-secgw is below::
- ./build/ipsec-secgw [EAL options] --
+ ./<build_target>/examples/dpdk-ipsec-secgw [EAL options] --
-p PORTMASK -P -u PORTMASK -j FRAMESIZE
-l -w REPLAY_WINOW_SIZE -e -a
--config (port,queue,lcore)[,(port,queue,lcore)]
@@ -127,6 +127,10 @@ compile the applications::
make -C ./examples/ipsec-secgw
+ meson:
+ meson configure -Dexamples=ipsec-secgw <build_target>
+ ninja -C <build_target>
+
Configuration File Syntax:
The ``-f CONFIG_FILE_PATH`` option enables the application read and
@@ -202,7 +206,7 @@ Cryptodev AES-NI algorithm validation matrix is showed in table below.
AESNI_MB device start cmd::
- ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 2048,0 --legacy-mem -a 0000:60:00.0
+ ./<build_target>/examples/dpdk-ipsec-secgw --socket-mem 2048,0 --legacy-mem -a 0000:60:00.0
--vdev=net_tap0,mac=fixed --vdev crypto_aesni_mb_pmd_1 --vdev=crypto_aesni_mb_pmd_2 -l 9,10,11 -n 6 -- -P --config "(0,0,10),(1,0,11)"
-u 0x1 -p 0x3 -f /root/dts/local_conf/ipsec_test.cfg
@@ -230,7 +234,7 @@ Cryptodev QAT algorithm validation matrix is showed in table below.
QAT device start cmd::
- ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 2048,0 --legacy-mem --vdev=net_tap0,mac=fixed -a 0000:60:00.0
+ ./<build_target>/examples/dpdk-ipsec-secgw --socket-mem 2048,0 --legacy-mem --vdev=net_tap0,mac=fixed -a 0000:60:00.0
-a 0000:1a:01.0 -l 9,10,11 -n 6 -- -P --config "(0,0,10),(1,0,11)" -u 0x1 -p 0x3
-f /root/dts/local_conf/ipsec_test.cfg
@@ -244,7 +248,7 @@ AES_GCM_PMD algorithm validation matrix is showed in table below.
AESNI_GCM device start cmd::
- ./examples/ipsec-secgw/build/ipsec-secgw --socket-mem 2048,0 --legacy-mem -a 0000:60:00.0 --vdev=net_tap0,mac=fixed
+ ./<build_target>/examples/dpdk-ipsec-secgw --socket-mem 2048,0 --legacy-mem -a 0000:60:00.0 --vdev=net_tap0,mac=fixed
--vdev crypto_aesni_gcm_pmd_1 --vdev=crypto_aesni_gcm_pmd_2 -l 9,10,11 -n 6 -- -P --config "(0,0,10),(1,0,11)"
-u 0x1 -p 0x3 -f /root/dts/local_conf/ipsec_test.cfg
@@ -80,7 +80,7 @@ Bind the interface to the driver ::
Start testpmd in a loop configuration ::
- # x86_64-native-linux-gcc/app/testpmd -l 1,2 -n 4 -a xxxx:xx:xx.x \
+ # ./<build_target>/app/dpdk-testpmd -l 1,2 -n 4 -a xxxx:xx:xx.x \
-- -i --port-topology=loop
Start packet forwarding ::
@@ -122,7 +122,7 @@ Grant permissions for all users to access the new character device ::
Start testpmd in a loop configuration ::
- $ x86_64-native-linux-gcc/app/testpmd -l 1,2 -n 4 -a xxxx:xx:xx.x --in-memory \
+ $ ./<build_target>/app/dpdk-testpmd -l 1,2 -n 4 -a xxxx:xx:xx.x --in-memory \
-- -i --port-topology=loop
Start packet forwarding ::
@@ -148,11 +148,13 @@ application.
Compile the application ::
- # cd $RTE_SDK/examples/helloworld && make
+ make: # cd $RTE_SDK/examples/helloworld && make
+ meson: meson configure -Dexamples=helloworld <build_target>;ninja -C <build_target>
Run the application ::
- $ $RTE_SDK/examples/helloworld/build/helloworld-shared --in-memory
+ 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.
@@ -75,7 +75,7 @@ Test Case 1: enable_mdd_dpdk_disable
5. Turn on testpmd and set mac forwarding mode::
- ./testpmd -c 0x0f -n 4 -- -i --portmask=0x3 --tx-offloads=0x1
+ ./<build_target>/app/dpdk-testpmd -c 0x0f -n 4 -- -i --portmask=0x3 --tx-offloads=0x1
testpmd> set fwd mac
testpmd> start
@@ -143,7 +143,7 @@ Test Case 2: enable_mdd_dpdk_enable
5. Turn on testpmd and set mac forwarding mode::
- ./testpmd -c 0x0f -n 4 -- -i --portmask=0x3 --tx-offloads=0x0
+ ./<build_target>/app/dpdk-testpmd -c 0x0f -n 4 -- -i --portmask=0x3 --tx-offloads=0x0
testpmd> set fwd mac
testpmd> start
@@ -211,7 +211,7 @@ Test Case 3: disable_mdd_dpdk_disable
5. Turn on testpmd and set mac forwarding mode::
- ./testpmd -c 0xf -n 4 -- -i --portmask=0x3 --tx-offloads=0x1
+ ./<build_target>/app/dpdk-testpmd -c 0xf -n 4 -- -i --portmask=0x3 --tx-offloads=0x1
testpmd> set fwd mac
testpmd> start
@@ -279,7 +279,7 @@ Test Case 4: disable_mdd_dpdk_enable
5. Turn on testpmd and set mac forwarding mode::
- ./testpmd -c 0xf -n 4 -- -i --portmask=0x3 --tx-offloads=0x0
+ ./<build_target>/app/dpdk-testpmd -c 0xf -n 4 -- -i --portmask=0x3 --tx-offloads=0x0
testpmd> set fwd mac
testpmd> start
@@ -86,7 +86,7 @@ dut_port_1 : "0000:05:00.1"
and 2 ports only in the application port mask (first port from the port
mask is used for RX and the other port in the core mask is used for TX)::
- ./build/qos_meter -c 1 -n 4 -- -p 0x3
+ ./<build_target>/examples/dpdk-qos_meter -c 1 -n 4 -- -p 0x3
Test Case: srTCM blind input color RED
======================================
@@ -37,7 +37,7 @@ QoS Scheduler Tests
The QoS Scheduler results are produced using ''qos_sched'' application.
The application has a number of command line options::
- ./qos_sched [EAL options] -- <APP PARAMS>
+ ./<build_target>/examples/dpdk-qos_sched [EAL options] -- <APP PARAMS>
Mandatory application parameters include:
-pfc “RX PORT, TX PORT, RX LCORE, WT LCORE, TX CORE”: Packet flow configuration.
@@ -92,7 +92,7 @@ Test Case: 1 pipe, 8 TCs
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
2. The traffic manage setting is configured in profile.cfg.
Set flows with QinQ inner vlan ID=0, which represents pipe 0.
@@ -164,7 +164,7 @@ Test Case: 4 pipe, 4 TCs
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
2. The traffic manage setting is configured in profile.cfg.
Set three flows with QinQ inner vlan ID=0/1/2/3, which represents pipe 0/1/2/3.
@@ -189,7 +189,7 @@ Test Case: 1 pipe, 12 TCs
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
2. The traffic manage setting is configured in profile.cfg.
change pipe profile 0, set tb rate and tc rate to 1/40.96 port rate::
@@ -253,7 +253,7 @@ Test Case: 1 pipe, set a TC rate to 0
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
2. The traffic manage setting is configured in profile.cfg.
change pipe profile 0, set tb rate and tc rate to 1/40.96 port rate::
@@ -304,7 +304,7 @@ Test Case: best effort TC12
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
2. The traffic manage setting is configured in profile.cfg.
Set flows with QinQ inner vlan ID=0, which represents pipe 0.
@@ -363,7 +363,7 @@ Test Case: 4096 pipes, 12 TCs
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,5,7 -n 4 -- -i --pfc "0,1,5,7" --cfg ../profile.cfg
2. The traffic manage setting is configured in profile.cfg.
Set flows with QinQ inner vlan ID=random, which represents pipe 0-4095.
@@ -426,7 +426,7 @@ Test Case: 4096 pipes, 12 TCs
3. If TX core defined::
- ./qos_sched -l 1,2,6,7 -n 4 -- -i --pfc "0,1,2,6,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,2,6,7 -n 4 -- -i --pfc "0,1,2,6,7" --cfg ../profile.cfg
The received rate can reach linerate, which is 13.89Mpps, no packets are dropped::
@@ -473,7 +473,7 @@ Test Case: qos_sched of two ports
1. This example with two packet flows configuration using different ports
but sharing the same core for QoS scheduler is given below::
- ./qos_sched -l 1,2,6,7 -n 4 -- --pfc "0,1,2,6,7" --pfc "1,0,2,6,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,2,6,7 -n 4 -- --pfc "0,1,2,6,7" --pfc "1,0,2,6,7" --cfg ../profile.cfg
2. The traffic manage setting is configured in profile.cfg.
Set flows with QinQ inner vlan ID=random, which represents pipe 0-4095.
@@ -623,7 +623,7 @@ so the two supports case can't be verified.*
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,2,5,7 -n 4 -- -i --pfc "0,1,2,5,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,2,5,7 -n 4 -- -i --pfc "0,1,2,5,7" --cfg ../profile.cfg
3. The generator settings:
Set IP dst address mode is random, and the mask is "255.255.255.0".
@@ -648,7 +648,7 @@ so the two supports case can't be verified.*
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,2,5,7 -n 4 -- -i --pfc "0,1,2,5,7" --cfg ../profile.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,2,5,7 -n 4 -- -i --pfc "0,1,2,5,7" --cfg ../profile.cfg
3. The generator settings:
Set IP dst address mode is random, and the mask is "255.255.255.0".
@@ -672,7 +672,7 @@ Test Case: Redistribution of unused pipe BW to other pipes within the same subpo
which creates one RX thread on lcore 5 reading from port 0
and a worker thread on lcore 7 writing to port 1::
- ./qos_sched -l 1,2,5,7 -n 4 -- -i --pfc "0,1,2,5,7" --cfg ../profile_ov.cfg
+ ./<build_target>/examples/dpdk-qos_sched -l 1,2,5,7 -n 4 -- -i --pfc "0,1,2,5,7" --cfg ../profile_ov.cfg
3. The generator settings:
Configure 4 flows:
@@ -51,7 +51,7 @@ Test Case: test_set_hash_key_toeplitz
#. Launch the ``testpmd`` application with the following arguments::
- ./testpmd -c ffffff -n 4 -- -i --portmask=0x6 --rxq=16 --txq=16
+ ./<build_target>/app/dpdk-testpmd -c ffffff -n 4 -- -i --portmask=0x6 --rxq=16 --txq=16
#. PMD fwd only receive the packets::
@@ -76,7 +76,7 @@ Test Case: dst (destination MAC) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -116,7 +116,7 @@ Test Case: src (source MAC) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -157,7 +157,7 @@ Test Case: type (EtherType or TPID) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -201,7 +201,7 @@ Test Case: protocol (protocol type) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -246,7 +246,7 @@ Test Case: icmp_type (ICMP message type) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -291,7 +291,7 @@ We tested type 3, code 3.
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -335,7 +335,7 @@ Test Case: tos (Type of Service) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -377,7 +377,7 @@ Test Case: ttl (time to live) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -418,7 +418,7 @@ Test Case: proto (IPv4 protocol) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -459,7 +459,7 @@ Test Case: src (IPv4 source) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -499,7 +499,7 @@ Test Case: dst (IPv4 destination) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -542,7 +542,7 @@ Test Case: tc (Traffic Class) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -583,7 +583,7 @@ Test Case: flow (Flow Code) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -624,7 +624,7 @@ Test Case: proto (IPv6 protocol/next header protocol) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -665,7 +665,7 @@ Test Case: hop (Hop Limit) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -704,7 +704,7 @@ Test Case: dst (IPv6 destination) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -744,7 +744,7 @@ Test Case: src (IPv6 source) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -788,7 +788,7 @@ Test Case: src (source port) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -826,7 +826,7 @@ Test Case: dst (destination port) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -866,7 +866,7 @@ Test Case: tag (SCTP header tag) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -907,7 +907,7 @@ Test Case: cksum (SCTP header checksum) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -950,7 +950,7 @@ Test Case: src (source port) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -991,7 +991,7 @@ Test Case: dst (destination port) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1032,7 +1032,7 @@ Test Case: flags (TCP flags) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1075,7 +1075,7 @@ Test Case: src (source port) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1115,7 +1115,7 @@ Test Case: dst (destination port) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1161,7 +1161,7 @@ We test them altogether as the tci and we test each field individually.
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1203,7 +1203,7 @@ Test Case: pcp (Priority Code Point) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1242,7 +1242,7 @@ NOTE: The only two possible values for dei are 0 and 1.
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1279,7 +1279,7 @@ Test Case: vid (VLAN identifier) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1320,7 +1320,7 @@ Test Case: tpid (Tag Protocol Identifier) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1364,7 +1364,7 @@ Test Case: vni (VXLAN network identifier) rule
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1423,7 +1423,7 @@ Test Case: passthru test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1465,7 +1465,7 @@ Test Case: flag test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1507,7 +1507,7 @@ Test Case: drop test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1550,7 +1550,7 @@ Test Case: test_shared
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1590,7 +1590,7 @@ Test Case: test_id
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1633,7 +1633,7 @@ Test Case: mac_swap test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1676,7 +1676,7 @@ Test Case: dec_ttl test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1719,7 +1719,7 @@ Test Case: jump test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1763,7 +1763,7 @@ Test Case: mark test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1806,7 +1806,7 @@ Test Case: queue test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1849,7 +1849,7 @@ Test Case: pf test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1892,7 +1892,7 @@ Test Case: test_original
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1932,7 +1932,7 @@ Test Case: test_id
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -1976,7 +1976,7 @@ Test Case: test_original
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2016,7 +2016,7 @@ Test Case: test_index
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2060,7 +2060,7 @@ Test Case: test_original
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2100,7 +2100,7 @@ Test Case: test_id
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2144,7 +2144,7 @@ Test Case: meter test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2187,7 +2187,7 @@ Test Case: security test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2231,7 +2231,7 @@ Test Case: of_set_mpls_ttl test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2274,7 +2274,7 @@ Test Case: of_dec_mpls_ttl test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2318,7 +2318,7 @@ Test Case: of_set_nw_ttl test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2362,7 +2362,7 @@ Test Case: of_dec_nw_ttl test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2405,7 +2405,7 @@ Test Case: of_copy_ttl_out test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2448,7 +2448,7 @@ Test Case: of_copy_ttl_in test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2491,7 +2491,7 @@ Test Case: of_pop_vlan test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2534,7 +2534,7 @@ Test Case: of_push_vlan test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2578,7 +2578,7 @@ Test Case: of_set_vlan_vid test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2621,7 +2621,7 @@ Test Case: of_set_vlan_pcp test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2664,7 +2664,7 @@ Test Case: of_pop_mpls test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2707,7 +2707,7 @@ Test Case: of_push_mpls test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2750,7 +2750,7 @@ Test Case: vxlan_encap
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2793,7 +2793,7 @@ Test Case: vxlan_decap
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2836,7 +2836,7 @@ Test Case: test_data
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2877,7 +2877,7 @@ Test Case: test_preserve
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2919,7 +2919,7 @@ Test Case: test_size
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -2964,7 +2964,7 @@ Test Case: test_data
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3005,7 +3005,7 @@ Test Case: test_size
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3049,7 +3049,7 @@ Test Case: set_ipv4_src test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3093,7 +3093,7 @@ Test Case: set_ipv4_dst test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3136,7 +3136,7 @@ Test Case: set_ipv6_src test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3181,7 +3181,7 @@ Test Case: set_ipv6_dst test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3226,7 +3226,7 @@ Test Case: test_udp
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3266,7 +3266,7 @@ Test Case: test_tcp
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3310,7 +3310,7 @@ Test Case: test_udp
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3350,7 +3350,7 @@ Test Case: test_tcp
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3392,7 +3392,7 @@ Test Case: set_ttl test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3435,7 +3435,7 @@ Test Case: set_mac_src test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3478,7 +3478,7 @@ Test Case: set_mac_dst test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3521,7 +3521,7 @@ Test Case: inc_tcp_seq test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3564,7 +3564,7 @@ Test Case: dec_tcp_seq test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3607,7 +3607,7 @@ Test Case: inc_tcp_ack test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3650,7 +3650,7 @@ Test Case: dec_tcp_ack test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3693,7 +3693,7 @@ Test Case: test_data
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3734,7 +3734,7 @@ Test Case: test_mask
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3776,7 +3776,7 @@ Test Case: test_index
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3820,7 +3820,7 @@ Test Case: test_data
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3861,7 +3861,7 @@ Test Case: test_mask
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3904,7 +3904,7 @@ Test Case: set_ipv4_dscp test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3948,7 +3948,7 @@ Test Case: set_ipv6_dscp test
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -3992,7 +3992,7 @@ Test Case: test_timeout
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -4032,7 +4032,7 @@ Test Case: test_reserved
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -4072,7 +4072,7 @@ Test Case: test_context
::
- build/testpmd -c 3 -- -i
+ ./<build_target>/app/dpdk-testpmd -c 3 -- -i
..
@@ -108,7 +108,7 @@ Test case 1: VF consume max queue number on one PF port
================================================================
1. Start the PF testpmd::
- ./testpmd -c f -n 4 -a 05:00.0 --file-prefix=test1 \
+ ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 05:00.0 --file-prefix=test1 \
--socket-mem 1024,1024 -- -i
2. Start the two testpmd to consume maximum queues::
@@ -120,10 +120,10 @@ Test case 1: VF consume max queue number on one PF port
The driver will alloc queues as power of 2, and queue must be equal or less than 16,
so the second VF testpmd can only start '--rxq=8 --txq=8'::
- ./testpmd -c 0xf0 -n 4 -a 05:02.0 -a 05:02.1 -a 05:02.2 -a... --file-prefix=test2 \
+ ./<build_target>/app/dpdk-testpmd -c 0xf0 -n 4 -a 05:02.0 -a 05:02.1 -a 05:02.2 -a... --file-prefix=test2 \
--socket-mem 1024,1024 -- -i --rxq=16 --txq=16
- ./testpmd -c 0xf00 -n 4 -a 05:05.7 --file-prefix=test3 \
+ ./<build_target>/app/dpdk-testpmd -c 0xf00 -n 4 -a 05:05.7 --file-prefix=test3 \
--socket-mem 1024,1024 -- -i --rxq=8 --txq=8
Check the Max possible RX queues and TX queues of the two VFs are both 16::
@@ -154,7 +154,7 @@ Test case 2: set max queue number per vf on one pf port
As the feature description describe, the max value of queue-num-per-vf is 8
for Both two and four ports Fortville NIC::
- ./testpmd -c f -n 4 -a 05:00.0,queue-num-per-vf=16 --file-prefix=test1 \
+ ./<build_target>/app/dpdk-testpmd -c f -n 4 -a 05:00.0,queue-num-per-vf=16 --file-prefix=test1 \
--socket-mem 1024,1024 -- -i
PF port failed to started with "i40e_pf_parameter_init():
@@ -52,7 +52,7 @@ Assuming that ports ``0`` and ``1`` of the test target are directly connected
to the traffic generator, launch the ``testpmd`` application with the following
arguments::
- ./build/app/testpmd -- -i --portmask=0x3
+ ./<build_target>/app/dpdk-testpmd -- -i --portmask=0x3
Start packet forwarding in the ``testpmd`` application with the ``start``
command. Then, for each port on the target make the Traffic Generator
@@ -64,14 +64,16 @@ Prerequisites
to the pools numbers(inclusive) and the VLAN user priority field increments from
0 to 7 (inclusive) for each VLAN ID.
- Build vmdq_dcb example,
- make -C examples/vmdq_dcb RTE_SDK=`pwd` T=x86_64-native-linuxapp-gcc
+ make: make -C examples/vmdq_dcb RTE_SDK=`pwd` T=x86_64-native-linuxapp-gcc
+ meson: ./<build_target>/examples/dpdk-vmdq_dcb -c 0xff -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4 --enable-rss
Test Case 1: Verify VMDQ & DCB with 32 Pools and 4 TCs
======================================================
1. Run the application as the following::
- ./examples/vmdq_dcb/build/vmdq_dcb_app -c 0xff -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4 --enable-rss
+ make: ./examples/vmdq_dcb/build/vmdq_dcb_app -c 0xff -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4 --enable-rss
+ meson: ./<build_target>/examples/dpdk-vmdq_dcb -c 0xff -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4 --enable-rss
2. Start traffic transmission using approx 10% of line rate.
3. After a number of seconds, e.g. 15, stop traffic, and ensure no traffic
@@ -92,10 +94,12 @@ Test Case 2: Verify VMDQ & DCB with 16 Pools and 8 TCs
======================================================
1. change CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM to 8 in "./config/common_linuxapp", rebuild DPDK.
+ meson: change "#define RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM 4" to 8 in config/rte_config.h, rebuild DPDK.
2. Repeat Test Case 1, with `--nb-pools 16` and `--nb-tcs 8` of the sample application::
- ./examples/vmdq_dcb/build/vmdq_dcb_app -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss
+ make: ./examples/vmdq_dcb/build/vmdq_dcb_app -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss
+ meson: ./<build_target>/examples/dpdk-vmdq_dcb -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss
Expected result:
- No packet loss is expected
@@ -103,10 +107,12 @@ Expected result:
- verify queue should be equal "vlan user priority value"
3. change CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM to 16 in "./config/common_linuxapp", rebuild DPDK.
+ meson: change "#define RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM 4" to 16 in config/rte_config.h, rebuild DPDK.
4. Repeat Test Case 1, with `--nb-pools 16` and `--nb-tcs 8` of the sample application::
- ./examples/vmdq_dcb/build/vmdq_dcb_app -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss
+ make: ./examples/vmdq_dcb/build/vmdq_dcb_app -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss
+ meson: ./<build_target>/examples/dpdk-vmdq_dcb -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss
Expected result:
- No packet loss is expected