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 74278A0093; Tue, 26 Apr 2022 05:15:25 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 48E61406A2; Tue, 26 Apr 2022 05:15:25 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id B632040691 for ; Tue, 26 Apr 2022 05:15:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650942923; x=1682478923; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=3xpZoCQ5QUqDS1n6GzENEjbE2WppMq46cEBbY8yr08w=; b=bW+GCybQV5y1dMYTA5eIJ0ANMHbT83Ky7wIkiuIF96sMXNojTHN4ZJzk oz39TE4YW1WwygN2T+XUYBz84DznaYg98v4MfkomHzTS2XL6bQ/RmCWt6 3N3prBaBrx/zkUxWFK6td3AtQ8R+Oa1ZjuwoeVhUo2HP1VrwWab/QJTuQ 3J/ExouHR8rz1jVo1GVbzSvsu01hINmI1LGQ3He245xmtzwqVYTFq184J QtVtWhGE6QgU6cQubdSQVsgZ9KMYpKyU0SZQk80kmX/+PcJT4iXKua0SP i8ZxWnWmYWYuxIL27LPlEIEWVNHXkB4WUF8A+kQGMrHueuIFsdsHLEq9D A==; X-IronPort-AV: E=McAfee;i="6400,9594,10328"; a="247362094" X-IronPort-AV: E=Sophos;i="5.90,290,1643702400"; d="scan'208";a="247362094" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Apr 2022 20:15:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,290,1643702400"; d="scan'208";a="532427078" Received: from dpdk-lijuan-1.sh.intel.com ([10.67.119.208]) by orsmga006.jf.intel.com with ESMTP; 25 Apr 2022 20:15:15 -0700 From: Lijuan Tu To: dts@dpdk.org Cc: Lijuan Tu Subject: [v2] test_plan: add l3fwd funtional test plan Date: Tue, 26 Apr 2022 11:12:36 +0800 Message-Id: <20220426031236.3959685-1-lijuan.tu@intel.com> X-Mailer: git-send-email 2.25.1 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 L3fwd is widely used for performance testing. Functional test cases are necessary for l3fwd quality. Signed-off-by: Lijuan Tu --- v2: fix doc building warning test_plans/index.rst | 1 + test_plans/l3fwd_func_test_plan.rst | 237 ++++++++++++++++++++++++++++ 2 files changed, 238 insertions(+) create mode 100644 test_plans/l3fwd_func_test_plan.rst diff --git a/test_plans/index.rst b/test_plans/index.rst index f8118d14..35143fb2 100644 --- a/test_plans/index.rst +++ b/test_plans/index.rst @@ -114,6 +114,7 @@ The following are the test plans for the DPDK DTS automated test system. l2fwd_test_plan l2tp_esp_coverage_test_plan l3fwd_test_plan + l3fwd_func_test_plan l3fwdacl_test_plan large_vf_test_plan link_flowctrl_test_plan diff --git a/test_plans/l3fwd_func_test_plan.rst b/test_plans/l3fwd_func_test_plan.rst new file mode 100644 index 00000000..e69e44a5 --- /dev/null +++ b/test_plans/l3fwd_func_test_plan.rst @@ -0,0 +1,237 @@ +.. SPDX-License-Identifier: BSD-3-Clause + Copyright 2022 Intel Corporation + +========================== +L3fwd Functional test plan +========================== + +Description +=========== + +The L3fwd application is a simple example of packet processing using +DPDK to demonstrate usage of poll and event mode packet I/O mechanism. +The application performs L3 forwarding. For more, please consult +`Data Plane Development Kit L3 Forwarding Sample Application +`_. + +Prerequisites +============= +Topology +-------- +It requires at least 1 port connected traffic generator:: + + Port0 --- TG0 + +2 ports is better:: + + Port0 --- TG0 + Port1 --- TG1 + + +Hardware +-------- +This suite focus on l3fwd application, so any standard Ethernet Network Adapter is qualified. + +Software +-------- +* dpdk l3fwd application +* scapy to send packets from traffic generator, which is usually another Ethernet Network Adapter. + +General Set Up +-------------- +Here assume that 0000:18:00.0 and 0000:18:00.1 are DUT ports, and ens785f0 and ens785f1 are tester interfaces. + +#. Build DPDK and l3fwd application:: + + # meson -Dexamples=l3fwd + # ninja -C + +#. Get the DUT ports and tester interfaces:: + + # ./usertools/dpdk-devbind.py -s + 0000:18:00.0 'Ethernet Controller E810-C for QSFP 1592' if=ens785f0 drv=ice unused=vfio-pci + 0000:18:00.1 'Ethernet Controller E810-C for QSFP 1592' if=ens785f1 drv=ice unused=vfio-pci + +#. Bind the DUT ports to vfio-pci:: + + # ./usertools/dpdk-devbind.py -b vfio-pci 0000:18:00.0 0000:18:00.1 + 0000:18:00.0 'Ethernet Controller E810-C for QSFP 1592' drv=vfio-pci unused=ice + 0000:18:00.1 'Ethernet Controller E810-C for QSFP 1592' drv=vfio-pci unused=ice + + +Test Case +========= + +The l3fwd application has a number of command line options, here list the key options will be tested:: + + ./dpdk-l3fwd [EAL options] -- -p PORTMASK + --rule_ipv4=FILE + --rule_ipv6=FILE + [-P] + [--lookup LOOKUP_METHOD] + --config(port,queue,lcore)[,(port,queue,lcore)] + [--rx-queue-size NPKTS] + [--tx-queue-size NPKTS] + ... + +Go through every options is not efficiency, therefore 3 combinations are created to make sure every key options are tested. + +.. table:: + + +-------------+--------------------+-------------+--------------+-------------+---------------+ + | Port number | Rx queues per port | Rule source | Lookup | Promise | Queue size | + +=============+====================+=============+==============+=============+===============+ + | 1 | 1 | default | default(lpm) | default(on) | default(1024) | + +-------------+--------------------+-------------+--------------+-------------+---------------+ + | 1 | 4 | file | em | enable | 2048 | + +-------------+--------------------+-------------+--------------+-------------+---------------+ + | 2 | 4 | file | em | enable | 2048 | + +-------------+--------------------+-------------+--------------+-------------+---------------+ + +The table shows: + +* No. 1 covers most default options with least port, it only requires 1 port. +* No. 2 covers the other situations against to default, it also requires 1 port. +* No. 3 is almost same as No.2 except it requires 2 ports. + +.. note:: + + * If there is only 1 port, choose test case 1 and 2 to test. + * If there are 2 ports, choose test case 1 and 3 to test. + +Packet pattern: + +* IPv4:: + + [Ether(dst="", src="")/IP(src="1.2.3.4",dst="")/Raw("x"*80)] + +* IPv6:: + + [Ether(dst="", src="")/IPv6(src="fe80::b696:91ff:fe9f:64b9",dst="")/Raw("x"*80)] + +.. note:: + + 20 packets with increased src_ip are used in every examination. + + +Test Case 1: 1 port 1 queue with default setting +------------------------------------------------ + +#. Launch l3fwd:: + + .//examples/dpdk-l3fwd -l -n 4 -- -p 0x1 --config="(0,0,)" + ./build/examples/dpdk-l3fwd -l 1 -n 4 -- -p 0x1 --config="(0,0,1)" --eth-dest=0,b4:96:91:9f:64:b9 + + Here list some output logs which helps you understand l3fwd. + + * The DUT port is 0000:18:00.0:: + + EAL: Probe PCI driver: net_ice (8086:1592) device: 0000:18:00.0 (socket 0) + + * The lookup method is lpm and use default table. DUT mac address is 40:A6:B7:7B:3F:00, the egress packets dst mac is 02:00:00:00:00:00:: + + Neither LPM, EM, or FIB selected, defaulting to LPM + L3FWD: Missing 1 or more rule files, using default instead + + * Every port creates 1 rx queue and 1 tx queue:: + + Creating queues: nb_rxq=1 nb_txq=1 + Address:40:A6:B7:7B:3F:00, Destination:02:00:00:00:00:00 + + * Route rules:: + + LPM: Adding route 198.18.0.0 / 24 (0) [0000:18:00.0] + LPM: Adding route 2001:200:: / 64 (0) [0000:18:00.0] + + * RX PATH "AVX2 OFFLOAD Vector Rx" is used:: + + ice_set_rx_function(): Using AVX2 OFFLOAD Vector Rx (port 0) + + * lcore 1 is used to polling port 0 rx queue 0:: + + L3FWD: -- lcoreid=1 portid=0 rxqueueid=0 + + * Link status, Packets sending to DUT have to wait port `link up`:: + + Port 0 Link up at 100 Gbps FDX Autoneg + +#. run tcpdump to capture packets on tester interface:: + + tcpdump -i -vvv -Q in -e + tcpdump -i ens2f0 -vvv -Q in -e + +#. TG send both 20 ipv4 and ipv6 packets which match the route table:: + + >>> sendp([Ether(dst="", src="")/IP(src="",dst="<198.168.0.x>")/Raw("x"*80)], iface="") + >>> sendp([Ether(dst="", src="")/IPv6(src="",dst="<2001:200::x>")/Raw("x"*80)], iface="") + + >>> sendp([Ether(dst="40:A6:B7:7B:3F:00", src="b4:96:91:9f:64:b9")/IP(src="1.2.3.4",dst="198.168.0.1")/Raw("x"*80)], iface="ens2f0") + >>> sendp([Ether(dst="40:A6:B7:7B:3F:00", src="b4:96:91:9f:64:b9")/IPv6(src="fe80::b696:91ff:fe9f:64b9",dst="2001:200::")/Raw("x"*80)], iface="ens2f0") + +#. Check if the packets forwarded to TG, get the packets informartion from tcpdump output:: + + 07:44:32.770005 40:a6:b7:7b:3f:00 (oui Unknown) > 02:00:00:00:00:00 (oui Unknown), ethertype IPv4 (0x0800), length 114: (tos 0x0, ttl 63, id 1, offset 0, flags [none], proto Options (0), length 100) + 1.2.3.4 > 198.168.0.1: hopopt 80 + 07:53:08.206002 40:a6:b7:7b:3f:00 (oui Unknown) > 02:00:00:00:00:00 (oui Unknown), ethertype IPv6 (0x86dd), length 134: (hlim 64, next-header unknown (59) payload length: 80) test > 2001:200::: no next header + + `Pass Criteria`: Both the IPv4 and IPv6 packets are matched with the the transmitted packets. + +Test Case 2: 1 port 4 queue with non-default setting +---------------------------------------------------- + +#. Launch l3fwd:: + + .//examples/dpdk-l3fwd -l -n 4 -- -p 0x1 --config="(0,0,),(0,1,),(0,2,),(0,3,)" -P --rule_ipv4="./examples/l3fwd/em_default_v4.cfg" --rule_ipv6="./examples/l3fwd/em_default_v6.cfg" --lookup=em --rx-queue-size=2048 --tx-queue-size=2048 + ./build/examples/dpdk-l3fwd -l 1,2 -n 4 -- -p 0x1 --config="(0,0,1),(0,1,1),(0,2,2),(0,3,2)" -P --rule_ipv4="./examples/l3fwd/em_default_v4.cfg" --rule_ipv6="./examples/l3fwd/em_default_v6.cfg" --lookup=em --rx-queue-size=2048 --tx-queue-size=2048 --parse-ptype + + "--parse-ptype" is optional, add it if DUT do not support to parse RTE_PTYPE_L3_IPV4_EXT and RTE_PTYPE_L3_IPV6_EXT. + + * Route rules:: + + EM: Adding route 198.18.0.0, 198.18.0.1, 9, 9, 17 (0) [0000:18:00.0] + +#. run tcpdump to capture packets on tester interface:: + + tcpdump -i -vvv -Q in -e + tcpdump -i ens2f0 -vvv -Q in -e + +#. TG send both ipv4 and ipv6 packets which match the route table and distributed to all queues:: + + >>> sendp([Ether(dst="", src="")/IP(src="",dst="<198.168.0.x>")/Raw("x"*80)], iface="") + >>> sendp([Ether(dst="", src="")/IPv6(src="",dst="")/Raw("x"*80)], iface="") + +#. Check if the packets forwarded to TG, get the packets informartion from tcpdump output:: + + 07:44:32.770005 40:a6:b7:7b:3f:00 (oui Unknown) > 02:00:00:00:00:00 (oui Unknown), ethertype IPv4 (0x0800), length 114: (tos 0x0, ttl 63, id 1, offset 0, flags [none], proto Options (0), length 100) + 1.2.3.4 > 198.168.0.1: hopopt 80 + 07:53:08.206002 40:a6:b7:7b:3f:00 (oui Unknown) > 02:00:00:00:00:00 (oui Unknown), ethertype IPv6 (0x86dd), length 134: (hlim 64, next-header unknown (59) payload length: 80) test > 2001:200::: no next header + + `Pass Criteria`: Both the IPv4 and IPv6 packets are matched with the the transmitted packets. + + +Test Case 3: 2 ports 4 queues with non-default setting +------------------------------------------------------ + +#. Launch l3fwd:: + + .//examples/dpdk-l3fwd -l -n 4 -- -p 0x3 --config="(0,0,),(0,1,),(0,2,, ,(0,3,),(1,0,),(1,1,),(1,2,, ,(1,3,)" -P --rule_ipv4="rule_ipv4.cfg" --rule_ipv6="rule_ipv6.cfg" --lookup=em --rx-queue-size=2048 --tx-queue-size=2048 + +#. run tcpdump to capture packets on tester interfaces:: + + tcpdump -i -vvv -Q in -e + tcpdump -i -vvv -Q in -e + +#. All TG 2 ports send both ipv4 and ipv6 packets which match the route table and distributed to all queues:: + + >>> sendp([Ether(dst="", src="")/IP(src="",dst="<198.168.0.x>")/Raw("x"*80)], iface="") + >>> sendp([Ether(dst="", src="")/IPv6(src="",dst="")/Raw("x"*80)], iface="") + >>> sendp([Ether(dst="", src="")/IP(src="",dst="<198.168.0.x>")/Raw("x"*80)], iface="") + >>> sendp([Ether(dst="", src="")/IPv6(src="",dst="")/Raw("x"*80)], iface="") + +#. Check if the packets forwarded to TG, run tcpdump to capture packets on tester interface:: + + 07:44:32.770005 40:a6:b7:7b:3f:00 (oui Unknown) > 02:00:00:00:00:00 (oui Unknown), ethertype IPv4 (0x0800), length 114: (tos 0x0, ttl 63, id 1, offset 0, flags [none], proto Options (0), length 100) + 1.2.3.4 > 198.168.0.1: hopopt 80 + 07:53:08.206002 40:a6:b7:7b:3f:00 (oui Unknown) > 02:00:00:00:00:00 (oui Unknown), ethertype IPv6 (0x86dd), length 134: (hlim 64, next-header unknown (59) payload length: 80) test > 2001:200::: no next header + + `Pass Criteria`: Both the IPv4 and IPv6 packets are matched with the the transmitted packets. -- 2.25.1