From patchwork Thu Feb 24 13:46:31 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yu Jiang X-Patchwork-Id: 108226 Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E961FA04A2; Thu, 24 Feb 2022 06:47:05 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9F9E741168; Thu, 24 Feb 2022 06:47:05 +0100 (CET) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id 8B3F240E5A for ; Thu, 24 Feb 2022 06:47:04 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645681624; x=1677217624; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=dljdgmU53ngdwkm6RIk+G2FEIK1GHN2Cgct62724qp0=; b=QpdX6UOQEs+hNGcgnGOjnK+OUrbQxMpwr2VHYawc+6+IieVTGWxuhTqB Ul9R4V5zHrShtfdwCA/1llVF2hy0SpIPlj2iJ0wlRiXBNnhQO7oYQXG9n fCsxSNeTSzlcs4/IaBtO62w6nWFnkBkeWUiUwSubGXPm6f8uFjqgkgSok kljspF5q3/sV+4a4Y+yMWDycOUvfPm5JENbbdPf0I0kUjgB7LLQMaTIsu kDTYOB4OVXf8xgPscexCA5YXX/zrWaGzHQul3cizHzjDm7fGBcHe2QlmU Qh1Y9jl9ckDUmfUxZZUI0gOS7yEdem3Uq08JC8KhakRhuMIIdR40B5WnX w==; X-IronPort-AV: E=McAfee;i="6200,9189,10267"; a="315382119" X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="315382119" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:04 -0800 X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="548590600" Received: from unknown (HELO localhost.localdomain) ([10.239.251.226]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:02 -0800 From: Yu Jiang To: lijuan.tu@intel.com, dts@dpdk.org Cc: Yu Jiang Subject: [dts][PATCH V3 1/5] test_plans/*: modify test plan to adapt meson build Date: Thu, 24 Feb 2022 13:46:31 +0000 Message-Id: <20220224134635.1501581-2-yux.jiang@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220224134635.1501581-1-yux.jiang@intel.com> References: <20220224134635.1501581-1-yux.jiang@intel.com> MIME-Version: 1.0 X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org test_plans/*: modify test plan to adapt meson build, including vf_pf_reset,vhost_qemu_mtu,vm2vm_virtio_user,vmdq_dcb Signed-off-by: Yu Jiang --- test_plans/vf_pf_reset_test_plan.rst | 22 +++++++++++----------- test_plans/vhost_qemu_mtu_test_plan.rst | 4 ++-- test_plans/vm2vm_virtio_user_test_plan.rst | 4 ++-- test_plans/vmdq_dcb_test_plan.rst | 4 ---- 4 files changed, 15 insertions(+), 19 deletions(-) diff --git a/test_plans/vf_pf_reset_test_plan.rst b/test_plans/vf_pf_reset_test_plan.rst index 574d4510..d3a9f505 100644 --- a/test_plans/vf_pf_reset_test_plan.rst +++ b/test_plans/vf_pf_reset_test_plan.rst @@ -90,7 +90,7 @@ Test Case 1: vf reset -- create two vfs on one pf 5. Run testpmd:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x0f -n 4 -- -i \ + .//app/dpdk-testpmd -c 0x0f -n 4 -- -i \ --portmask=0x3 testpmd> set fwd mac testpmd> start @@ -159,11 +159,11 @@ Test Case 2: vf reset -- create two vfs on one pf, run testpmd separately 2. Start testpmd on two vf ports:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 \ + .//app/dpdk-testpmd -c 0xf -n 4 \ --socket-mem 1024,1024 -a 81:02.0 --file-prefix=test1 \ -- -i --eth-peer=0,00:11:22:33:44:12 \ - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf0 -n 4 \ + .//app/dpdk-testpmd -c 0xf0 -n 4 \ --socket-mem 1024,1024 -a 81:02.1 --file-prefix=test2 \ -- -i @@ -207,7 +207,7 @@ Test Case 3: vf reset -- create one vf on each pf 3. Start one testpmd on two vf ports:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x0f -n 4 -- -i \ + .//app/dpdk-testpmd -c 0x0f -n 4 -- -i \ --portmask=0x3 4. Start forwarding:: @@ -234,7 +234,7 @@ Test Case 4: vlan rx restore -- vf reset all ports 1. Execute the step1-step3 of test case 1, then start the testpmd:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x0f -n 4 -- -i \ + .//app/dpdk-testpmd -c 0x0f -n 4 -- -i \ --portmask=0x3 testpmd> set fwd mac @@ -289,7 +289,7 @@ test Case 5: vlan rx restore -- vf reset one port 1. Execute the step1-step3 of test case 1, then start the testpmd:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x0f -n 4 -- -i \ + .//app/dpdk-testpmd -c 0x0f -n 4 -- -i \ --portmask=0x3 testpmd> set fwd mac @@ -429,7 +429,7 @@ Test Case 7: vlan tx restore 2. Run testpmd:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x0f -n 4 -- -i \ + .//app/dpdk-testpmd -c 0x0f -n 4 -- -i \ --portmask=0x3 3. Add tx vlan offload on VF1 port, take care the first param is port, @@ -473,7 +473,7 @@ test Case 8: MAC address restore 3. Start testpmd on two vf ports:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x0f -n 4 \ + .//app/dpdk-testpmd -c 0x0f -n 4 \ -- -i --portmask=0x3 4. Add MAC address to the vf0 ports:: @@ -544,7 +544,7 @@ test Case 9: vf reset (two vfs passed through to one VM) bind them to igb_uio driver,and then start testpmd:: ./usertools/dpdk-devbind.py -b igb_uio 00:05.0 00:05.1 - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x0f -n 4 \ + .//app/dpdk-testpmd -c 0x0f -n 4 \ -a 00:05.0 -a 00:05.1 -- -i --portmask=0x3 5. Add MAC address to the vf0 ports, set it in mac forward mode:: @@ -618,14 +618,14 @@ test Case 10: vf reset (two vfs passed through to two VM) bind the port to igb_uio, then start testpmd on vf0 port:: ./tools/dpdk_nic_bind.py --bind=igb_uio 00:05.0 - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 4 \ + .//app/dpdk-testpmd -c 0xf -n 4 \ -- -i --eth-peer=0,vf1port_macaddr \ login vm1, got VF1 pci device id in vm1, assume it's 00:06.0, bind the port to igb_uio, then start testpmd on vf1 port:: ./tools/dpdk_nic_bind.py --bind=igb_uio 00:06.0 - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf0 -n 4 \ + .//app/dpdk-testpmd -c 0xf0 -n 4 \ -- -i 5. Add vlan on vf0 in vm0, and set fwd mode:: diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst b/test_plans/vhost_qemu_mtu_test_plan.rst index 60b01cfb..62c2f7f8 100644 --- a/test_plans/vhost_qemu_mtu_test_plan.rst +++ b/test_plans/vhost_qemu_mtu_test_plan.rst @@ -46,7 +46,7 @@ Test Case: Test the MTU in virtio-net ===================================== 1. Launch the testpmd by below commands on host, and config mtu:: - ./testpmd -c 0xc -n 4 \ + .//app/dpdk-testpmd -c 0xc -n 4 \ --vdev 'net_vhost0,iface=vhost-net,queues=1' \ -- -i --txd=512 --rxd=128 --nb-cores=1 --port-topology=chained testpmd> set fwd mac @@ -70,7 +70,7 @@ Test Case: Test the MTU in virtio-net 4. Bind the virtio driver to igb_uio, launch testpmd in VM, and verify the mtu in port info is 9000:: - ./testpmd -c 0x03 -n 3 \ + .//app/dpdk-testpmd -c 0x03 -n 3 \ -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip testpmd> set fwd mac testpmd> start diff --git a/test_plans/vm2vm_virtio_user_test_plan.rst b/test_plans/vm2vm_virtio_user_test_plan.rst index 6fc5f89f..c3aa328e 100644 --- a/test_plans/vm2vm_virtio_user_test_plan.rst +++ b/test_plans/vm2vm_virtio_user_test_plan.rst @@ -1599,13 +1599,13 @@ Test Case 24: packed virtqueue vm2vm vectorized-tx path multi-queues test indire 1. Launch vhost by below command:: - ./x86_64-native-linuxapp-gcc/app/testpmd -l 1-2 -n 4 --no-pci \ + .//app/dpdk-testpmd -l 1-2 -n 4 --no-pci \ --vdev 'eth_vhost0,iface=vhost-net,queues=1' --vdev 'eth_vhost1,iface=vhost-net1,queues=1' -- \ -i --nb-cores=1 --no-flush-rx 2. Launch virtio-user1 by below command:: - ./x86_64-native-linuxapp-gcc/app/testpmd -n 4 -l 7-8 --no-pci --file-prefix=virtio1 --force-max-simd-bitwidth=512 \ + .//app/dpdk-testpmd -n 4 -l 7-8 --no-pci --file-prefix=virtio1 --force-max-simd-bitwidth=512 \ --vdev=net_virtio_user1,mac=00:01:02:03:04:05,path=./vhost-net1,queues=1,packed_vq=1,mrg_rxbuf=1,in_order=1,vectorized=1,queue_size=256 \ -- -i --nb-cores=1 --txd=256 --rxd=256 testpmd>set fwd rxonly diff --git a/test_plans/vmdq_dcb_test_plan.rst b/test_plans/vmdq_dcb_test_plan.rst index 1c9b82ef..a4beaa93 100644 --- a/test_plans/vmdq_dcb_test_plan.rst +++ b/test_plans/vmdq_dcb_test_plan.rst @@ -64,7 +64,6 @@ 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: make -C examples/vmdq_dcb RTE_SDK=`pwd` T=x86_64-native-linuxapp-gcc meson: .//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 @@ -72,7 +71,6 @@ Test Case 1: Verify VMDQ & DCB with 32 Pools and 4 TCs 1. Run the application as the following:: - make: ./examples/vmdq_dcb/build/vmdq_dcb_app -c 0xff -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4 --enable-rss meson: .//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. @@ -98,7 +96,6 @@ Test Case 2: Verify VMDQ & DCB with 16 Pools and 8 TCs 2. Repeat Test Case 1, with `--nb-pools 16` and `--nb-tcs 8` of the sample application:: - make: ./examples/vmdq_dcb/build/vmdq_dcb_app -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss meson: .//examples/dpdk-vmdq_dcb -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss Expected result: @@ -111,7 +108,6 @@ Expected result: 4. Repeat Test Case 1, with `--nb-pools 16` and `--nb-tcs 8` of the sample application:: - make: ./examples/vmdq_dcb/build/vmdq_dcb_app -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss meson: .//examples/dpdk-vmdq_dcb -c 0xff -n 4 -- -p 0x3 --nb-pools 16 --nb-tcs 8 --enable-rss Expected result: From patchwork Thu Feb 24 13:46:32 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yu Jiang X-Patchwork-Id: 108227 Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C2B52A0353; Thu, 24 Feb 2022 06:47:07 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BD2FA4115F; Thu, 24 Feb 2022 06:47:07 +0100 (CET) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id 57C0F40E5A for ; Thu, 24 Feb 2022 06:47:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645681626; x=1677217626; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=mgfavaX6Zmew4L/DJv1/p/6v98xjvxkAatVgOlDhUxE=; b=PL60euhR7YDldlHKgG9Va3XpIjPA3j0Q9Fh9k2v7Ja7g1CGQ8ncCn3Yc AJ74AU5NHeyKMp2hQAx6OLZCZrHDnnObyqf2s2JGLKppoaOJ1OwP1vUOU LntrtFiZ4CHeHQUkSBwjYmZ+p0VXN2+xxh141UeBJxT6AGoOEcRScgqsf uXmDNd97zpwMvHSFNMj3F6JUVxbzuRIY0O9id/2M/w67ee3VliWFObrox qOkrr04mdZipyqJFE724Iuzt1cd8Jyn2RfRq0kw/eSipmJ7o5cO3BZORy UnlUgOHX5z4rdOg4JiLyMpsz35hGxLboBEdAtV8isjPmmBJ4VP7Vy+3+u g==; X-IronPort-AV: E=McAfee;i="6200,9189,10267"; a="315382128" X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="315382128" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:06 -0800 X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="548590621" Received: from unknown (HELO localhost.localdomain) ([10.239.251.226]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:04 -0800 From: Yu Jiang To: lijuan.tu@intel.com, dts@dpdk.org Cc: Yu Jiang Subject: [dts][PATCH V3 2/5] test_plans/*: modify test plan to adapt meson build Date: Thu, 24 Feb 2022 13:46:32 +0000 Message-Id: <20220224134635.1501581-3-yux.jiang@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220224134635.1501581-1-yux.jiang@intel.com> References: <20220224134635.1501581-1-yux.jiang@intel.com> MIME-Version: 1.0 X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org test_plans/*: modify test plan to adapt meson build, including linux_modules,metrics,multicast,shutdown_api Signed-off-by: Yu Jiang --- 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 ;ninja -C Run the application :: - make: $ $RTE_SDK/examples/helloworld/build/helloworld-shared --in-memory meson: $ .//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 + .//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 |.//examples/dpdk-ipv4_multicast -c 0x40 -n 3 -- -p PORTMASK -q 2 | ++-----+------------------------------------------------------------------------------------+ +|2 |.//examples/dpdk-ipv4_multicast -c 0x400040 -n 3 -- -p PORTMASK -q 1 | ++-----+------------------------------------------------------------------------------------+ +|3 |.//examples/dpdk-ipv4_multicast -c 0x30 -n 3 -- -p PORTMASK -q 1 | ++-----+------------------------------------------------------------------------------------+ +|4 |.//examples/dpdk-ipv4_multicast -c 0x40 -n 3 -- -p PORTMASK -q 2 | ++-----+------------------------------------------------------------------------------------+ +|5 |.//examples/dpdk-ipv4_multicast -c 0x400040 -n 3 -- -p PORTMASK -q 1 | ++-----+------------------------------------------------------------------------------------+ +|6 |.//examples/dpdk-ipv4_multicast -c 0x30 -n 3 -- -p PORTMASK -q 1 | ++-----+------------------------------------------------------------------------------------+ +|7 |.//examples/dpdk-ipv4_multicast -c 0x40 -n 3 -- -p PORTMASK -q 2 | ++-----+------------------------------------------------------------------------------------+ +|8 |.//examples/dpdk-ipv4_multicast -c 0x400040 -n 3 -- -p PORTMASK -q 1 | ++-----+------------------------------------------------------------------------------------+ +|9 |.//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. From patchwork Thu Feb 24 13:46:33 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yu Jiang X-Patchwork-Id: 108228 Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E3B70A0353; Thu, 24 Feb 2022 06:47:09 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DDEFC41156; Thu, 24 Feb 2022 06:47:09 +0100 (CET) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id 249AC41171 for ; Thu, 24 Feb 2022 06:47:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645681628; x=1677217628; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=km0tfUXdh+ArAyhIMiDDXBc0AZ2mq+XSG+r24gJfpzM=; b=IcA+g/IjJ9DhUhYtfQ+uEEEQph2Bf/BVszdKRUAQWlPfItPTEcW9wgaC MNK8taFZqu395OQ/wBGRRlnSpnCKrQk9vFo5PuSLos4IgD66h5Yb3zFqK tKOSoFPHpmW12QD9WTbpv8VuGsG95b1Gplzee53YMBBpQXy9RbqK8fnxc 0DkbMcqaYqYuBj+87ZBlj63vbP3drJBUteE5dKGvdOGif+QMT3lTbzrVi S50CgwxIcH7/x/60VjONudRmFu6iiWslDKnx8f5qIuokLdqHk/T+h/MXN Vkw+IXdnDtjv6YTzKiEAg0OZCikuR6busISWUpBcjJDZJAbG7ZUV7g4BJ Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10267"; a="315382130" X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="315382130" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:07 -0800 X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="548590629" Received: from unknown (HELO localhost.localdomain) ([10.239.251.226]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:06 -0800 From: Yu Jiang To: lijuan.tu@intel.com, dts@dpdk.org Cc: Yu Jiang Subject: [dts][PATCH V3 3/5] test_plans/*: modify test plan to adapt meson build Date: Thu, 24 Feb 2022 13:46:33 +0000 Message-Id: <20220224134635.1501581-4-yux.jiang@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220224134635.1501581-1-yux.jiang@intel.com> References: <20220224134635.1501581-1-yux.jiang@intel.com> MIME-Version: 1.0 X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org test_plans/*: modify test plan to adapt meson build, including iavf,ipsec_gw_and_library,keep_alive,kernelpf_iavf Signed-off-by: Yu Jiang --- test_plans/iavf_test_plan.rst | 8 ++++---- test_plans/ipsec_gw_and_library_test_plan.rst | 2 -- test_plans/keep_alive_test_plan.rst | 13 ++----------- test_plans/kernelpf_iavf_test_plan.rst | 2 +- 4 files changed, 7 insertions(+), 18 deletions(-) diff --git a/test_plans/iavf_test_plan.rst b/test_plans/iavf_test_plan.rst index c055cd83..ddd7fbb9 100644 --- a/test_plans/iavf_test_plan.rst +++ b/test_plans/iavf_test_plan.rst @@ -54,7 +54,7 @@ Prerequisites 2. Start testpmd on host to configure VF ports' mac:: - ./x86_64-native-linuxapp-gcc/app/testpmd -l 1-5 -n 4 -- -i + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1-5 -n 4 -- -i testpmd>set vf mac addr 0 0 00:12:34:56:78:01 testpmd>set vf mac addr 1 0 00:12:34:56:78:02 @@ -79,7 +79,7 @@ Test case: VF basic RX/TX --------------------------- 1. Start testpmd on VM:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x3 -n 1 -- -i + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0x3 -n 1 -- -i 2. Check and verify packets which received and forwarded @@ -89,7 +89,7 @@ Test Cases: VF mac filter Start testpmd on VM:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x3 -n 1 -- -i + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0x3 -n 1 -- -i Test Case: unicast test ------------------------ @@ -141,7 +141,7 @@ Test Cases: VF VLAN feature vlan filter only work with promisc mode off Start testpmd on VM:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x3 -n 1 -- -i + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0x3 -n 1 -- -i Test Case: vlan filter --------------------------- diff --git a/test_plans/ipsec_gw_and_library_test_plan.rst b/test_plans/ipsec_gw_and_library_test_plan.rst index 1cd80783..8d51b684 100644 --- a/test_plans/ipsec_gw_and_library_test_plan.rst +++ b/test_plans/ipsec_gw_and_library_test_plan.rst @@ -125,8 +125,6 @@ The test commands of ipsec-secgw is below:: compile the applications:: - make -C ./examples/ipsec-secgw - meson: meson configure -Dexamples=ipsec-secgw ninja -C diff --git a/test_plans/keep_alive_test_plan.rst b/test_plans/keep_alive_test_plan.rst index 81c1c74f..41b5e4e0 100644 --- a/test_plans/keep_alive_test_plan.rst +++ b/test_plans/keep_alive_test_plan.rst @@ -49,15 +49,6 @@ Compiling the Application ========================= To compile the application: - -Go to the sample application directory:: - - export RTE_SDK=/path/to/rte_sdk cd ${RTE_SDK}/examples/keep_alive - -Set the target (a default target is used if not specified). For example:: - - export RTE_TARGET=x86_64-native-linuxapp-gcc - See the DPDK Getting Started Guide for possible RTE_TARGET values. Build the application:: @@ -69,7 +60,7 @@ Running the Application The application has a number of command line options:: - ./build/l2fwd-keepalive [EAL options] -- -p PORTMASK [-q NQ] [-K PERIOD] [-T PERIOD] + .//examples/dpdk-l2fwd-keepalive [EAL options] -- -p PORTMASK [-q NQ] [-K PERIOD] [-T PERIOD] where, @@ -80,6 +71,6 @@ where, To run the application in linuxapp environment with 4 lcores, 16 ports 8 RX queues per lcore and a ping interval of 10ms, issue the command:: - ./build/l2fwd-keepalive -c f -n 4 -- -q 8 -p ffff -K 10 + .//examples/dpdk-l2fwd-keepalive -c f -n 4 -- -q 8 -p ffff -K 10 Refer to the DPDK Getting Started Guide for general information on running applications and the Environment Abstraction Layer (EAL) options. diff --git a/test_plans/kernelpf_iavf_test_plan.rst b/test_plans/kernelpf_iavf_test_plan.rst index 45c217e4..9c10b125 100644 --- a/test_plans/kernelpf_iavf_test_plan.rst +++ b/test_plans/kernelpf_iavf_test_plan.rst @@ -653,7 +653,7 @@ Bind VFs to vfio-pci:: Start l3fwd power with one queue per port:: - ./examples/l3fwd-power/build/l3fwd-power -l 6,7 -n 4 -- \ + .//examples/dpdk-l3fwd-power -l 6,7 -n 4 -- \ -p 0x3 --config '(0,0,6),(1,0,7)' Send one packet to VF0 and VF1, check that thread on core6 and core7 waked up:: From patchwork Thu Feb 24 13:46:34 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yu Jiang X-Patchwork-Id: 108229 Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 10E72A0353; Thu, 24 Feb 2022 06:47:12 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0BE3A41170; Thu, 24 Feb 2022 06:47:12 +0100 (CET) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id E029441170 for ; Thu, 24 Feb 2022 06:47:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645681630; x=1677217630; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=xQ+WmK3yXyhyInae7R9NmyDb4mCockBJ06R2MuyjIMA=; b=IgMRArSnvnEacs2QG11nibtyyZ1nqbCsT1vYIVkXzurfQmNT7iiSvdXq XxDFT+TUTNj9PQWqwkd2LexIzuXHkuM/K2xW5ONjzMj8NkdCn1quteYtn I1if6vown9YZpMGUj2fYLGEl2f0Vf9m18kWPt+iJe0aXkB8IykuCYH1HS wQmklIJ4/fTVaE1jg2KJfz5Uve+AdX2/A94jZx+0PPdgCf36mzMD5/lN8 eIGlUajrtlMgBZNaGouzbjJ79t8UPSOdJJ/V/XIfHNfY8yUMOt0UUtPa0 xPfk61o6dvsHWhN22Bv4KWGFAP4vkQ7lXv0OmTHgQ+RWGW6AFNnZjK9aA A==; X-IronPort-AV: E=McAfee;i="6200,9189,10267"; a="315382134" X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="315382134" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:09 -0800 X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="548590658" Received: from unknown (HELO localhost.localdomain) ([10.239.251.226]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:08 -0800 From: Yu Jiang To: lijuan.tu@intel.com, dts@dpdk.org Cc: Yu Jiang Subject: [dts][PATCH V3 4/5] test_plans/*: modify test plan to adapt meson build Date: Thu, 24 Feb 2022 13:46:34 +0000 Message-Id: <20220224134635.1501581-5-yux.jiang@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220224134635.1501581-1-yux.jiang@intel.com> References: <20220224134635.1501581-1-yux.jiang@intel.com> MIME-Version: 1.0 X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org test_plans/*: modify test plan to adapt meson build, including ABI_stable,enable_package_download_in_ice_driver, external_mempool_handler,flow_classify,generic_flow_api Signed-off-by: Yu Jiang --- test_plans/ABI_stable_test_plan.rst | 9 +-------- ...nable_package_download_in_ice_driver_test_plan.rst | 8 ++++---- test_plans/external_mempool_handler_test_plan.rst | 10 +++++----- test_plans/flow_classify_test_plan.rst | 11 ++++++----- test_plans/generic_flow_api_test_plan.rst | 10 +++++----- 5 files changed, 21 insertions(+), 27 deletions(-) diff --git a/test_plans/ABI_stable_test_plan.rst b/test_plans/ABI_stable_test_plan.rst index ae0eb7b9..5408e2a9 100644 --- a/test_plans/ABI_stable_test_plan.rst +++ b/test_plans/ABI_stable_test_plan.rst @@ -47,13 +47,7 @@ Compiling Steps =============== Compile shared library/application from DPDK xx.11 release. -Change the option in config/common_base configuration file:: - - CONFIG_RTE_BUILD_SHARED_LIB=y - -And then, compile the DPDK:: - - make install -j T=x86_64-native-linuxapp-gcc +CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=shared ;ninja -C Keep this DPDK folder as , e.g. . @@ -65,7 +59,6 @@ Setup library path in environment:: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH, -meson: CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=shared ;ninja -C Common Test Steps ================= diff --git a/test_plans/enable_package_download_in_ice_driver_test_plan.rst b/test_plans/enable_package_download_in_ice_driver_test_plan.rst index 6de17a0b..b81e4e79 100644 --- a/test_plans/enable_package_download_in_ice_driver_test_plan.rst +++ b/test_plans/enable_package_download_in_ice_driver_test_plan.rst @@ -67,7 +67,7 @@ Test case 1: Download the package successfully 2. Start the testpmd:: - ./testpmd -c 0x3fe -n 6 -- -i --nb-cores=8 --rxq=8 --txq=8 \ + .//app/dpdk-testpmd -c 0x3fe -n 6 -- -i --nb-cores=8 --rxq=8 --txq=8 \ --port-topology=chained The testpmd can be started normally without any fail information. @@ -103,7 +103,7 @@ Test case 2: Driver enters Safe Mode successfully 2. Start testpmd:: - ./testpmd -c 0x3fe -n 6 \ + .//app/dpdk-testpmd -c 0x3fe -n 6 \ -a PORT0_PCI,safe-mode-support=1 -a PORT1_PCI,safe-mode-support=1 \ -- -i --nb-cores=8 --rxq=8 --txq=8 --port-topology=chained @@ -144,7 +144,7 @@ Test case 3: Driver enters Safe Mode failed 2. Start testpmd:: - ./testpmd -c 0x3fe -n 6 -- -i --nb-cores=8 --rxq=8 --txq=8 \ + .//app/dpdk-testpmd -c 0x3fe -n 6 -- -i --nb-cores=8 --rxq=8 --txq=8 \ --port-topology=chained There will be an error reported:: @@ -177,7 +177,7 @@ Compile DPDK and testpmd:: Launch testpmd with 1 default interface and 1 specific interface:: - ./x86_64-native-linux-gcc/app/testpmd -l 6-9 -n 4 -a 18:00.0 -a b1:00.0 --log-level=8 -- -i + .//app/dpdk-testpmd -l 6-9 -n 4 -a 18:00.0 -a b1:00.0 --log-level=8 -- -i In this case, b1:00.0 interface is specific interface. diff --git a/test_plans/external_mempool_handler_test_plan.rst b/test_plans/external_mempool_handler_test_plan.rst index 2f821364..c773dc0b 100644 --- a/test_plans/external_mempool_handler_test_plan.rst +++ b/test_plans/external_mempool_handler_test_plan.rst @@ -54,7 +54,7 @@ Test Case 1: Multiple producers and multiple consumers 3. Start testpmd with two ports and start forwarding:: - testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff + .//app/dpdk-testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff testpmd> set fwd mac testpmd> start @@ -75,7 +75,7 @@ Test Case 2: Single producer and Single consumer 3. Start testpmd with two ports and start forwarding:: - testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff + .//app/dpdk-testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff testpmd> set fwd mac testpmd> start @@ -96,7 +96,7 @@ Test Case 3: Single producer and Multiple consumers 3. Start testpmd with two ports and start forwarding:: - testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff + .//app/dpdk-testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff testpmd> set fwd mac testpmd> start @@ -117,7 +117,7 @@ Test Case 4: Multiple producers and single consumer 3. Start testpmd with two ports and start forwarding:: - testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff + .//app/dpdk-testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff testpmd> set fwd mac testpmd> start @@ -138,7 +138,7 @@ Test Case 4: Stack mempool handler 3. Start testpmd with two ports and start forwarding:: - testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff + .//app/dpdk-testpmd -c 0x6 -n 4 -- -i --portmask=0x3 --tx-offloads=0x8fff testpmd> set fwd mac testpmd> start diff --git a/test_plans/flow_classify_test_plan.rst b/test_plans/flow_classify_test_plan.rst index 07236172..4175ed7c 100644 --- a/test_plans/flow_classify_test_plan.rst +++ b/test_plans/flow_classify_test_plan.rst @@ -168,14 +168,15 @@ Compilation: ------------ steps:: - cd $DPDK_PATH - export RTE_TARGET=$DPDK_PATH - export RTE_SDK=`pwd` - make -C examples/flow_classify + CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static + ninja -C + + meson configure -Dexamples=flow_classify + ninja -C Flow classify bin file under:: - $DPDK_PATH/examples/flow_classify/build/flow_classify + /examples/dpdk-flow_classify rule config file(default):: diff --git a/test_plans/generic_flow_api_test_plan.rst b/test_plans/generic_flow_api_test_plan.rst index 98baec62..6fd039a0 100644 --- a/test_plans/generic_flow_api_test_plan.rst +++ b/test_plans/generic_flow_api_test_plan.rst @@ -222,12 +222,12 @@ Test case: Fortville fdir for ipv4 testpmd> set verbose 1 testpmd> start - ./x86_64-native-linuxapp-gcc/app/testpmd -c 1e0000 -n 4 -a 05:02.0 --file-prefix=vf0 --socket-mem=1024,1024 -- -i --rxq=4 --txq=4 --disable-rss --pkt-filter-mode=perfect + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 1e0000 -n 4 -a 05:02.0 --file-prefix=vf0 --socket-mem=1024,1024 -- -i --rxq=4 --txq=4 --disable-rss --pkt-filter-mode=perfect testpmd> set fwd rxonly testpmd> set verbose 1 testpmd> start - ./x86_64-native-linuxapp-gcc/app/testpmd -c 1e00000 -n 4 -a 05:02.1 --file-prefix=vf1 --socket-mem=1024,1024 -- -i --rxq=4 --txq=4 --disable-rss --pkt-filter-mode=perfect + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 1e00000 -n 4 -a 05:02.1 --file-prefix=vf1 --socket-mem=1024,1024 -- -i --rxq=4 --txq=4 --disable-rss --pkt-filter-mode=perfect testpmd> set fwd rxonly testpmd> set verbose 1 testpmd> start @@ -2009,7 +2009,7 @@ Test case: Dual vlan(QinQ) 1. set up testpmd with Fortville NICs:: - ./dpdk-testpmd -c 0x1ffff -n 4 -- -i --coremask=0x1fffe --portmask=0x1 --rxq=16 --txq=16 --tx-offloads=0x8fff + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0x1ffff -n 4 -- -i --coremask=0x1fffe --portmask=0x1 --rxq=16 --txq=16 --tx-offloads=0x8fff 2. verbose configuration:: @@ -2107,7 +2107,7 @@ Test Case: 10GB Multiple filters 1. set up testpmd with Fortville NICs:: - ./dpdk-testpmd -l 1,2,3,4,5,6,7,8 -n 4 -- -i --disable-rss --rxq=16 --txq=16 + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1,2,3,4,5,6,7,8 -n 4 -- -i --disable-rss --rxq=16 --txq=16 2. verbose configuration:: @@ -2220,7 +2220,7 @@ This case is designed for NIC(niantic). Default use 64 queues for test Launch the app ``testpmd`` with the following arguments:: - ./dpdk-testpmd -l 1,2,3,4,5 -n 4 -- -i --disable-rss --rxq=64 --txq=64 --portmask=0x3 --nb-cores=4 --total-num-mbufs=263168 + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1,2,3,4,5 -n 4 -- -i --disable-rss --rxq=64 --txq=64 --portmask=0x3 --nb-cores=4 --total-num-mbufs=263168 testpmd>set stat_qmap rx 0 0 0 testpmd>set stat_qmap rx 1 0 0 From patchwork Thu Feb 24 13:46:35 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yu Jiang X-Patchwork-Id: 108230 Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 34707A0353; Thu, 24 Feb 2022 06:47:25 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2EF4E4116A; Thu, 24 Feb 2022 06:47:25 +0100 (CET) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id E25DD40E5A for ; Thu, 24 Feb 2022 06:47:23 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645681644; x=1677217644; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=kDgl+CqJacY9Zpe7HakFRGAcUYLrpe9CXnMzcYg/aPo=; b=h3bwGeYVHuGmU/Xph+bMmvynOBPsjKPKJj5x2Fdc99TrMdkPcfH5s+Dl CH7YEn8/dd7sNUmog20W8XpVHCGjUsEs+IisHLrKPjzZxD7VmMGJv7Uss xO4QvoBzmQSa0qqFolalxgZzhydN6PHpx5yElLy4UARLywvnbhH6oTWEQ TEFR28igJ8DgFYzb+riG03av7qhuepMqmEt6EPz/1ET+yC5hCEParpH76 KIU2Bd+W6QFNeqY9vRgbtUn6vIROI/5kLHOIanoOLnn156SYpiB3yx9Up pmq1Z88A5o75tRe1SPc5NxJqoFuK8B7YbZQlVGQqufE0g4qzGoUWmsrWZ w==; X-IronPort-AV: E=McAfee;i="6200,9189,10267"; a="315382140" X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="315382140" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:11 -0800 X-IronPort-AV: E=Sophos;i="5.88,393,1635231600"; d="scan'208";a="548590695" Received: from unknown (HELO localhost.localdomain) ([10.239.251.226]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 21:47:09 -0800 From: Yu Jiang To: lijuan.tu@intel.com, dts@dpdk.org Cc: Yu Jiang Subject: [dts][PATCH V3 5/5] test_plans/*: modify test plan to adapt meson build Date: Thu, 24 Feb 2022 13:46:35 +0000 Message-Id: <20220224134635.1501581-6-yux.jiang@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220224134635.1501581-1-yux.jiang@intel.com> References: <20220224134635.1501581-1-yux.jiang@intel.com> MIME-Version: 1.0 X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org test_plans/*: modify test plan to adapt meson build, including telemetry,vdev_primary_secondary,vf_packet_rxtx Signed-off-by: Yu Jiang --- test_plans/telemetry_test_plan.rst | 14 +++++++---- .../vdev_primary_secondary_test_plan.rst | 24 ++++++++++++------- test_plans/vf_packet_rxtx_test_plan.rst | 2 +- 3 files changed, 25 insertions(+), 15 deletions(-) diff --git a/test_plans/telemetry_test_plan.rst b/test_plans/telemetry_test_plan.rst index 07983206..4dd63681 100644 --- a/test_plans/telemetry_test_plan.rst +++ b/test_plans/telemetry_test_plan.rst @@ -58,9 +58,13 @@ Prerequisites 1. Enable the telemetry API by modifying the following config option before building DPDK:: Python >= 2.5 - Jansson library for JSON serialization - CONFIG_RTE_LIBRTE_TELEMETRY=y and libjansson should be available - make install RTE_SDK=`pwd` T=x86_64-native-linuxapp-gcc + Jansson library for JSON serialization, libjansson should be available + RTE_LIB_TELEMETRY is 1 by default in /rte_build_config.h: + #define RTE_LIB_TELEMETRY 1 + + Build DPDK: + CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static + ninja -C 2. Configiure PF @@ -68,7 +72,7 @@ Prerequisites insmod x86_64-native-linuxapp-gcc/kmod/igb_uio.ko; 3. Launch testpmd as the primary application with the ``telemetry`` - ./app/testpmd --telemetry + .//app/dpdk-testpmd --telemetry 4. Launch the ``telemetry`` python script with a client filepath : @@ -95,7 +99,7 @@ Test case: basic connection for testpmd and telemetry client:: For the building meson shared and make shared . tested command should be used when run on ubuntu OS make share and meson version:: - $ ./app/testpmd -c f -n 4 -d librte_mempool_ring.so -d librte_telemetry.so --telemetry --socket-mem=1024,1024 -- -i + $ .//app/dpdk-testpmd -c f -n 4 -d librte_mempool_ring.so -d librte_telemetry.so --telemetry --socket-mem=1024,1024 -- -i 3.Run Python terminal: python dpdk-telemetry-client.py diff --git a/test_plans/vdev_primary_secondary_test_plan.rst b/test_plans/vdev_primary_secondary_test_plan.rst index cb78d192..b9ffd030 100644 --- a/test_plans/vdev_primary_secondary_test_plan.rst +++ b/test_plans/vdev_primary_secondary_test_plan.rst @@ -91,14 +91,20 @@ The secondary symmetric_mp instances must also have these parameters specified, and the first two must be the same as those passed to the primary instance, or errors result. -For example, to run a set of four symmetric_mp instances, running on lcores 1-4, all +For example, +to build symmetric_mp:: + + meson configure -Dexamples=multi_process/symmetric_mp + ninja -C + +to run a set of four symmetric_mp instances, running on lcores 1-4, all performing level-2 forwarding of packets between ports 0 and 1, the following commands can be used (assuming run as root):: - ./build/symmetric_mp -c 2 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=0 - ./build/symmetric_mp -c 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=1 - ./build/symmetric_mp -c 8 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=2 - ./build/symmetric_mp -c 10 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=3 + .//examples/dpdk-symmetric_mp -c 2 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=0 + .//examples/dpdk-symmetric_mp -c 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=1 + .//examples/dpdk-symmetric_mp -c 8 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=2 + .//examples/dpdk-symmetric_mp -c 10 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=3 To run only 1 or 2 instances, the above parameters to the 1 or 2 instances being run should remain the same, except for the ``num-procs`` value, which should be @@ -168,8 +174,8 @@ SW preparation: Change one line of the symmetric_mp sample and rebuild:: 4. Launch two process by example:: - ./examples/multi_process/symmetric_mp/build/symmetric_mp -l 1 -n 4 --proc-type=auto -- -p 3 --num-procs=2 --proc-id=0 - ./examples/multi_process/symmetric_mp/build/symmetric_mp -l 2 -n 4 --proc-type=secondary -- -p 3 --num-procs=2 --proc-id=1 + .//examples/dpdk-symmetric_mp -l 1 -n 4 --proc-type=auto -- -p 3 --num-procs=2 --proc-id=0 + .//examples/dpdk-symmetric_mp -l 2 -n 4 --proc-type=secondary -- -p 3 --num-procs=2 --proc-id=1 5. Quit all process, check the packets number in rx/tx statistic like below for both primary process and secondary process:: @@ -206,7 +212,7 @@ Test Case 2: Virtio-pmd primary and secondary process hotplug test 4. Start sample code as primary process:: - ./examples/multi_process/hotplug_mp/build/hotplug_mp --proc-type=auto -- -p 3 --num-procs=2 --proc-id=0 + .//examples/dpdk-symmetric_mp --proc-type=auto -- -p 3 --num-procs=2 --proc-id=0 example> list list all etherdev 0 0000:00:05.0 @@ -214,7 +220,7 @@ Test Case 2: Virtio-pmd primary and secondary process hotplug test 5. Start sample code as secondary process:: - ./examples/multi_process/hotplug_mp/build/hotplug_mp --proc-type=secondary -- -p 3 --num-procs=2 --proc-id=1 + .//examples/dpdk-symmetric_mp --proc-type=secondary -- -p 3 --num-procs=2 --proc-id=1 example> list list all etherdev 0 0000:00:05.0 diff --git a/test_plans/vf_packet_rxtx_test_plan.rst b/test_plans/vf_packet_rxtx_test_plan.rst index a3ff86cb..69b18038 100644 --- a/test_plans/vf_packet_rxtx_test_plan.rst +++ b/test_plans/vf_packet_rxtx_test_plan.rst @@ -311,7 +311,7 @@ this case pf in kernel testpmd> set fwd mac testpmd> start 7. On vm 1:: - ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 1 -- -i + ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0xf -n 1 -- -i 8. On vm0::