From patchwork Thu Feb 24 11:23:21 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yu Jiang X-Patchwork-Id: 108219 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 7EB81A0353; Thu, 24 Feb 2022 04:23:58 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 76D474115E; Thu, 24 Feb 2022 04:23:58 +0100 (CET) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id 100DF40DF6 for ; Thu, 24 Feb 2022 04:23:56 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645673037; x=1677209037; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=mgfavaX6Zmew4L/DJv1/p/6v98xjvxkAatVgOlDhUxE=; b=UXr63jvF0TpUIjzK9Edu4eZjAosSOQJAA1U7r5jx8RV0zI0Ezz+/wKNR aeyq7pBMLn4q6f4H9QfLx0toNchEdllq1KLKjsaKE5nJISNb/C1J2R14V TVYJcIa5R6IoisuV1gGDYAOIqQ4fw8ubbZqNWwWrtVFONrzpzfrF0fg7C 6erSYSYyzwu8EzR8QxSp2CplRMb8vDMZaP3+Eyn+RRntrMh2v3+7yW+c9 JkmSS+gwQqL6fWnbcwIhdOH8EOHd4DS90dpanZYAYcxSlGk8pUYulbjgL pVYJfUoUxvA5oeV7atcudHZ8uh6Uc+MSay+pMVQT1ik913sKe3AIbnU88 g==; X-IronPort-AV: E=McAfee;i="6200,9189,10267"; a="252059800" X-IronPort-AV: E=Sophos;i="5.88,392,1635231600"; d="scan'208";a="252059800" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 19:23:56 -0800 X-IronPort-AV: E=Sophos;i="5.88,392,1635231600"; d="scan'208";a="639567165" Received: from unknown (HELO localhost.localdomain) ([10.239.251.226]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 19:23:54 -0800 From: Yu Jiang To: lijuan.tu@intel.com, dts@dpdk.org Cc: Yu Jiang Subject: [dts][PATCH V2 2/6] test_plans/*: modify test plan to adapt meson build Date: Thu, 24 Feb 2022 11:23:21 +0000 Message-Id: <20220224112325.1488073-3-yux.jiang@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220224112325.1488073-1-yux.jiang@intel.com> References: <20220224112325.1488073-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.