From patchwork Thu Feb 24 11:23:24 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yu Jiang X-Patchwork-Id: 108222 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 798ECA0353; Thu, 24 Feb 2022 04:24:03 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6E5B04115D; Thu, 24 Feb 2022 04:24:03 +0100 (CET) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id A9B4F41168 for ; Thu, 24 Feb 2022 04:24:01 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645673041; x=1677209041; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=kDgl+CqJacY9Zpe7HakFRGAcUYLrpe9CXnMzcYg/aPo=; b=XE2YbWQAWG/N01YSddo+cQaOFo2OLlCZ8zjIM62jBVclxzyC7N6lkiAH nYTnQcC8Qxjt5/97v0Yc7xBQ2VEsgCplp3wa5Q50ulUVSGf/HzRLBB1kC JInLwPaiWbIqVOGsW+uMQeOb2ryzWHe6eqTuwaObylYvpQALiwm5yeOgV pvMMFBiTjWWc1sSxpKxdPeNP29D4g4r60Y8VP1P58eOzycwGPdNC4lmq7 tjxO1pUWDMHp4aUCCjTPPJDuCxSIzz1rJox4mkZruHDruyJMrjJ7NpRqT df8F/OKi9HgSFyGysdwoEdjMGcTfG+RX86vni6zCdH1KeS/62VwUQN58J Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10267"; a="252059814" X-IronPort-AV: E=Sophos;i="5.88,392,1635231600"; d="scan'208";a="252059814" 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:24:00 -0800 X-IronPort-AV: E=Sophos;i="5.88,392,1635231600"; d="scan'208";a="639567197" 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:59 -0800 From: Yu Jiang To: lijuan.tu@intel.com, dts@dpdk.org Cc: Yu Jiang Subject: [dts][PATCH V2 5/6] test_plans/*: modify test plan to adapt meson build Date: Thu, 24 Feb 2022 11:23:24 +0000 Message-Id: <20220224112325.1488073-6-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 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::