From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2D8B0A00C4; Tue, 3 Jan 2023 09:40:00 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 256E540A82; Tue, 3 Jan 2023 09:40:00 +0100 (CET) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mails.dpdk.org (Postfix) with ESMTP id 3AD7D40689 for ; Tue, 3 Jan 2023 09:39:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1672735198; x=1704271198; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=qvgo6qYJu2pQtnfszTTAyKeZoiVKHlxzfIUneOwpMjM=; b=dfS/JNzl+Q9LmUjTnyJDRlh62YWVGiBOspER1Sh9B3UIoyPY8W+g7oEr 0lkOr948HXYPAkttKBAQq7pNVsc91PeDFvIN3XGjSMFhrC+sirirc6y52 q0mvW+hyri8TzliJAFKCsS0mS/QrfG+JPbrtr+w3aKZ+N7+g3bKnne4Yw ce8aywkzca6i5miAC1b/QOJeJPYpYYPbrIIO6Re0C+l2NY6oC2DhOeceq lqLAu51iSRb121sAdYl6sIvm7mTPsoIqhyCo/vKMzZ0/UVYy9GduOp2rD bTrGulkIcIYMtY2QdMOdkJHjH2BfnTWiqexB4Jl5Pz/jRlHjPb96PaGq3 Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10578"; a="322847054" X-IronPort-AV: E=Sophos;i="5.96,296,1665471600"; d="scan'208";a="322847054" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Jan 2023 00:39:57 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10578"; a="654706411" X-IronPort-AV: E=Sophos;i="5.96,296,1665471600"; d="scan'208";a="654706411" Received: from dpdk-lijuan-icelake4.sh.intel.com ([10.67.119.188]) by orsmga002.jf.intel.com with ESMTP; 03 Jan 2023 00:39:56 -0800 From: Yingya Han To: dts@dpdk.org Cc: Yingya Han Subject: [dts][PATCH V1 1/9]test_plans: add l3fwd_lpm_ipv4_rfc2544 test plan Date: Tue, 3 Jan 2023 08:39:43 +0000 Message-Id: <20230103083951.1553786-2-yingyax.han@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230103083951.1553786-1-yingyax.han@intel.com> References: <20230103083951.1553786-1-yingyax.han@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 Signed-off-by: Yingya Han --- .../l3fwd_lpm_ipv4_rfc2544_test_plan.rst | 151 ++++++++++++++++++ 1 file changed, 151 insertions(+) create mode 100644 test_plans/l3fwd_lpm_ipv4_rfc2544_test_plan.rst diff --git a/test_plans/l3fwd_lpm_ipv4_rfc2544_test_plan.rst b/test_plans/l3fwd_lpm_ipv4_rfc2544_test_plan.rst new file mode 100644 index 00000000..29b16b3e --- /dev/null +++ b/test_plans/l3fwd_lpm_ipv4_rfc2544_test_plan.rst @@ -0,0 +1,151 @@ +.. SPDX-License-Identifier: BSD-3-Clause + Copyright(c) 2022 Intel Corporation + +======================================================== +L3 forwarding rfc2544 test in LPM mode with IPV4 packets +======================================================== + +RFC2544 Zero packet loss test case: Used to determine the DUT throughput as defined in +RFC1242(https://www.ietf.org/rfc/rfc1242.txt). Note RFC6201 +https://www.ietf.org/rfc/rfc6201.txt has updated RFC2544 and RFC1242. Please check the link +for more details. In this case, RFC2544 test uses DPDK l3fwd as test application. + +Prerequisites +============= + +Topology +-------- +It requires at least 1 port connected traffic generator:: + Port0 --- TG0 + +2 ports:: + Port0 --- TG0 + Port1 --- TG1 + +4 ports:: + Port0 --- TG0 + Port1 --- TG1 + Port2 --- TG2 + Port3 --- TG3 + +Hardware +-------- +This suite focus on l3fwd application, so any standard Ethernet Network Adapter is qualified. + +Software +-------- +dpdk: git clone http://dpdk.org/git/dpdk +trex: git clone http://trex-tgn.cisco.com/trex/release/v2.93.tar.gz + + +Test Case +========= +Send a specific number of frames at a specific rate through the DUT and then +count the frames that are transmitted by the DUT. If the count of offered frames is not equal +to the count of received frames, the rate of the offered stream is reduced and the test is rerun. +The throughput is the fastest rate at which the count of test frames transmitted by the DUT is +equal to the number of test frames sent to it by the test equipment. + +The l3fwd application has a number of command line options, here list the key options will be tested:: + + ./dpdk-l3fwd [EAL options] -- -p PORTMASK + [--force-max-simd-bitwidth=max-simd-bitwidth] + --config(port,queue,lcore)[,(port,queue,lcore)] + [--rx-queue-size NPKTS] + [--tx-queue-size NPKTS] + [--parse-ptype] + [-L]|[-E] + ... + Note: + --force-max-simd-bitwidth: This setting is used to determine the vector path for component selection. + And the default is avx2. + --rx-queue-size: Rx queue size in decimal and default is 1024. + --tx-queue-size: Tx queue size in decimal and default is 1024. + --parse-ptype: Optional, set to use software to analyze packet type. + Without this option, hardware will check the packet type. + [-L]|[-E]: L3fwd uses the parameters "-L" and "-E" to correspond to LPM and EM modes respectively. + And the default is LPM mode. + +Common Steps +------------ +1. Bind tested ports to vfio-pci:: + + #./usertools/dpdk-devbind.py -s + 0000:17:00.0 'Device 1592' if=ens5f0 drv=ice unused=vfio-pci + #./usertools/dpdk-devbind.py -b vfio-pci + #./usertools/dpdk-devbind.py -b vfio-pci 0000:17:00.0 + +2. Configure traffic generator to send traffic + + Routing table for IPv4 packets + - In LPM mode, the LPM table used for packet routing is: + + +-------+-----------------------+ + | # | LPM prefix (IP/length)| + +=======+=======================+ + | 0 | 198.18.0.0/24 | + +-------+-----------------------+ + | 1 | 198.18.1.0/24 | + +-------+-----------------------+ + | 2 | 198.18.2.0/24 | + +-------+-----------------------+ + | 3 | 198.18.3.0/24 | + +-------+-----------------------+ + + The flows need to be configured and started by the traffic generator: + - IPv4 packets + + +------+---------+------------+---------+ + | Flow | Traffic | IPv4 | IPv4 | + | | Gen. | Dst. | Src. | + | | Port | Address | Address | + +======+=========+============+=========+ + | 1 | TG0 | 198.18.1.1 | Any Ip | + +------+---------+------------+---------+ + | 2 | TG1 | 198.18.0.1 | Any Ip | + +------+---------+------------+---------+ + | 3 | TG2 | 198.18.3.1 | Any Ip | + +------+---------+------------+---------+ + | 4 | TG3 | 198.18.2.1 | Any Ip | + +------+---------+------------+---------+ + + Set the packet length : 64 bytes-1518 bytes + The IPV4 Src Address increase with the num 1024. + +3. Test result table + + +-----------+------------+-------------+---------+ + | Fwd_core | Frame Size | Throughput | Rate | + +===========+============+=============+=========+ + | 1C/1T | 64 | xxxxx Mpps | xxx % | + +-----------+------------+-------------+---------+ + | 1C/1T | ... | xxxxx Mpps | xxx % | + +-----------+------------+-------------+---------+ + | 2C/2T | 64 | xxxxx Mpps | xxx % | + +-----------+------------+-------------+---------+ + | 2C/2T | ... | xxxxx Mpps | xxx % | + +-----------+------------+-------------+---------+ + | 4C/4T | 64 | xxxxx Mpps | xxx % | + +-----------+------------+-------------+---------+ + | 4C/4T | ... | xxxxx Mpps | xxx % | + +-----------+------------+-------------+---------+ + | 8C/8T | 64 | xxxxx Mpps | xxx % | + +-----------+------------+-------------+---------+ + | 8C/8T | ... | xxxxx Mpps | xxx % | + +-----------+------------+-------------+---------+ + + +Test Case: test_perf_rfc2544_ipv4_lpm +------------------------------------- + +1. Bind PF ports to dpdk driver as common step 1. + +2. Launch l3fwd:: + + /examples/dpdk-l3fwd -l 5-8 -n 8 --force-max-simd-bitwidth=512 \ + -- -p 0x1 --config "(0,0,5),(0,1,6),(0,2,7),(0,3,8)" --rx-queue-size 1024 \ + --tx-queue-size 1024 + +3. Configure traffic generator to send traffic as common step 2. + +4. Record Test results as common step 3. -- 2.34.1