From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 44EB1A04F5; Fri, 19 Jun 2020 08:20:14 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3C64EFEB; Fri, 19 Jun 2020 08:20:14 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 297BAE07 for ; Fri, 19 Jun 2020 08:20:12 +0200 (CEST) IronPort-SDR: YTI0zX+FzCErQOqdiESr3UF8828E5gx4abms1RuktfNgeesZKPlXOnFTt7Y2fpbkH4/caNZ7gS sWL+rGW49Erg== X-IronPort-AV: E=McAfee;i="6000,8403,9656"; a="140391493" X-IronPort-AV: E=Sophos;i="5.75,253,1589266800"; d="scan'208";a="140391493" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jun 2020 23:20:11 -0700 IronPort-SDR: uHdZfI9ro00Te7vQkbdRrvj2gV+jK6m98Cp5Tvdg4q348i9ytEQCnwdJeI4wQdZFl6nVaAAV2u TsTtZmjndxEw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,253,1589266800"; d="scan'208";a="263788902" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga008.fm.intel.com with ESMTP; 18 Jun 2020 23:20:11 -0700 Received: from fmsmsx111.amr.corp.intel.com (10.18.116.5) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.439.0; Thu, 18 Jun 2020 23:20:11 -0700 Received: from shsmsx154.ccr.corp.intel.com (10.239.6.54) by fmsmsx111.amr.corp.intel.com (10.18.116.5) with Microsoft SMTP Server (TLS) id 14.3.439.0; Thu, 18 Jun 2020 23:20:10 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.85]) by SHSMSX154.ccr.corp.intel.com ([169.254.7.221]) with mapi id 14.03.0439.000; Fri, 19 Jun 2020 14:20:08 +0800 From: "Tu, Lijuan" To: "Mo, YufengX" , "dts@dpdk.org" , "Chen, Zhaoyan" CC: "Mo, YufengX" Thread-Topic: [dts] [PATCH V1 1/2] tests/dcf_lifecycle: update test plan Thread-Index: AQHWRFEVbalYBMekBEeVW1mTaLJuFqjfeq2w Date: Fri, 19 Jun 2020 06:20:08 +0000 Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC5FD78@SHSMSX101.ccr.corp.intel.com> References: <20200617024325.23247-1-yufengx.mo@intel.com> <20200617024325.23247-2-yufengx.mo@intel.com> In-Reply-To: <20200617024325.23247-2-yufengx.mo@intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] [PATCH V1 1/2] tests/dcf_lifecycle: update test plan X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 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 Sender: "dts" Applied the series, thanks -----Original Message----- From: dts On Behalf Of yufengmx Sent: 2020=1B$BG/=1B(B6=1B$B7n=1B(B17=1B$BF|=1B(B 10:43 To: dts@dpdk.org; Chen, Zhaoyan Cc: Mo, YufengX Subject: [dts] [PATCH V1 1/2] tests/dcf_lifecycle: update test plan update test plan. Signed-off-by: yufengmx --- ...e_test.rst =3D> dcf_lifecycle_test_plan.rst} | 60 +++++++++---------- 1 file changed, 30 insertions(+), 30 deletions(-) rename test_plans/{dcf_= lifecycle_test.rst =3D> dcf_lifecycle_test_plan.rst} (93%) diff --git a/test_plans/dcf_lifecycle_test.rst b/test_plans/dcf_lifecycle_t= est_plan.rst similarity index 93% rename from test_plans/dcf_lifecycle_test.rst rename to test_plans/dcf_life= cycle_test_plan.rst index c7d66c6..4f32a9f 100644 --- a/test_plans/dcf_lifecycle_test.rst +++ b/test_plans/dcf_lifecycle_test_plan.rst @@ -47,13 +47,13 @@ The DCF can act as a special VF talking to the kernel P= F over the same virtchannel mailbox to configure the underlying device (po= rt) for the VFs. =20 The test suite covers the lifecycle of DCF context in Kernel PF, such as -= launch, and exit, switch rules handling, reseting, and exception exit. +launch, and exit, switch rules handling, resetting, and exception exit. =20 =20 Configuration =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 -NIC: 2x25G or 2x100G, serveral TC need breakout mode. +NIC: 2x25G or 2x100G, several TC need breakout mode. NIC should have 2 PF ports at least, and connect to tester's ports. =20 Topology @@ -106,8 +106,7 @@ Launch dpdk on the VF, request DCF mode :: =20 Expected: VF get DCF mode. There are outputs in testpmd launching :: =20 - EAL: PCI device 0000:18:01.0 on NUMA socket 0 - EAL: probe driver: 8086:1889 net_ice_dcf + EAL: Probe PCI driver: net_ice_dcf (8086:1889) device: 0000:18:01.0=20 + (socket 0) =20 =20 TC02: DCF on 2 PFs, 1 trust VF on each PF @@ -134,11 +133,9 @@ Launch dpdk= on the VF on each PF, request DCF mode :: =20 Expected: VF get DCF mode. There are outputs in each testpmd launching :: =20 - EAL: PCI device 0000:18:01.0 on NUMA socket 0 - EAL: probe driver: 8086:1889 net_ice_dcf + EAL: Probe PCI driver: net_ice_dcf (8086:1889) device: 0000:18:01.0=20 + (socket 0) =20 - EAL: PCI device 0000:18:11.0 on NUMA socket 0 - EAL: probe driver: 8086:1889 net_ice_dcf + EAL: Probe PCI driver: net_ice_dcf (8086:1889) device: 0000:18:11.0=20 + (socket 0) =20 =20 TC03: Check only VF zero can get DCF mode @@ -159,13 +156,13 @@ Launch dpd= k on the VF, request DCF mode :: =20 Expected: VF can NOT get DCF mode. testpmd should provide a friendly outpu= t :: =20 - ice_dcf_get_vf_resource(): Fail to get response of OP_GET_VF_RESOURCE + ice_dcf_get_vf_resource(): Failed to get response of=20 + OP_GET_VF_RESOURCE ice_dcf_init_hw(): Failed to get VF resource ice_dcf_dev_init(): Failed to init DCF hardware =20 Error message in dmesg :: =20 - ice 0000:18:00.0: Only VF0 can request for DCF. + ice 0000:18:00.0: VF 1 requested DCF capability, but only VF 0 is=20 + allowed to request DCF capability ice 0000:18:00.0: VF 1 failed opcode 3, retval: -5 =20 =20 @@ -187,13 +184,13 @@ Launch dpdk on the VF, request DCF mode :: =20 Expected: VF can NOT get DCF mode. testpmd should provide a friendly outpu= t :: =20 - ice_dcf_get_vf_resource(): Fail to get response of OP_GET_VF_RESOURCE + ice_dcf_get_vf_resource(): Failed to get response of=20 + OP_GET_VF_RESOURCE ice_dcf_init_hw(): Failed to get VF resource ice_dcf_dev_init(): Failed to init DCF hardware =20 Error message in dmesg :: =20 - ice 0000:18:00.0: DCF needs to be trusted. + ice 0000:18:00.0: VF needs to be trusted to configure DCF=20 + capability ice 0000:18:00.0: VF 0 failed opcode 3, retval: -5 =20 =20 @@ -269,7 +266,8 @@ Launch another testpmd on the VF1, and start mac forwar= d :: =20 ./x86_64-native-linuxapp-gcc/app/testpmd -l 11-14 -n 4 -w 18:01.1 --fi= le-prefix=3Dvf -- -i set verbose 1 - set fwd macstart + set fwd mac + start =20 Set switch rule to VF1 0000:18:01.1 from DCF :: =20 @@ -280,7 +278,7 @@ Send a scapy packet to VF1 :: p =3D Ether(dst=3D'xx:xx:xx:xx:xx:xx')/IP(src=3D'192.168.0.2', dst=3D'= 192.168.0.3')/Raw(64*'x') sendp(p, iface=3D'testeri0', count=3D1) =20 -Check VF1 received the packet. Stats shows 1 packet received and forwarded= . :: +Check VF1 received the packet. Stats shows 1 packet received and forwarded= :: =20 show port stats all =20 @@ -317,7 +315,8 @@ Launch another testpmd on the VF1, and start mac forwar= d :: =20 ./x86_64-native-linuxapp-gcc/app/testpmd -l 11-14 -n 4 -w 18:01.1 --fi= le-prefix=3Dvf -- -i set verbose 1 - set fwd macstart + set fwd mac + start =20 Set switch rule to VF1 0000:18:01.1 from DCF :: =20 @@ -337,11 +336,11 @@ Kill DCF process :: ps -ef |grep testpmd #Check the process id kill -9 =20 -Send scapy packet again. Check VF1 can't receive the packet :: +Send scapy packet again. DCF flow rule is still valid, check VF1 can recei= ve the packet :: =20 show port stats all =20 -Expect: VF1 can't receive the packet +Expect: VF1 can receive the packet =20 =20 TC13: Launch 2nd DCF process on the same VF @@ -350,7 +349,7 @@ TC13: Laun= ch 2nd DCF process on the same VF Launch 2nd DCF process on the same VF, P= F shall reject the request. DPDK does not support to open 2nd DCF PMD driver on same VF. =20 -Generate 4 VFs on PF +Generate 4 VFs on PF :: =20 echo 4 > /sys/bus/pci/devices/0000:18:00.0/sriov_numvfs =20 @@ -460,7 +459,8 @@ Launch another testpmd on the VF1, and start mac forwar= d :: =20 ./x86_64-native-linuxapp-gcc/app/testpmd -l 11-14 -n 4 -w 18:01.1 -w 1= 8:01.2 --file-prefix=3Dvf -- -i set verbose 1 - set fwd macstart + set fwd mac + start =20 Set switch rule to VF1 0000:18:01.1 and VF2 0000:18:01.2 from DCF :: =20 @@ -484,7 +484,7 @@ Reset PF by lanconf command:: Select "SV Menu" and then select "Reset Menu" Select "PF Reset" to trigger PF reset event =20 -Send scapy packet again. Check VF1 can't receive the packet +Send scapy packet again. Check VF1 can't receive the packet:: =20 show port stats all =20 @@ -560,6 +560,7 @@ Remove ADQ on PF :: tc qdisc del dev enp24s0f0 root mqprio tc qdisc del dev enp24s0f0 ingress tc qdisc show dev enp24s0f0 + ethtool -K enp24s0f0 hw-tc-offload off =20 Launch dpdk on the VF, request DCF mode :: =20 @@ -568,8 +569,7 @@ Launch dpdk on the VF, request DCF mode :: =20 Expect: testpmd can launch successfully. DCF mode can be grant :: =20 - EAL: PCI device 0000:18:01.0 on NUMA socket 0 - EAL: probe driver: 8086:1889 net_ice_dcf + EAL: Probe PCI driver: net_ice_dcf (8086:1889) device: 0000:18:01.0=20 + (socket 0) =20 =20 TC20: When DCF mode enabled, ADQ setting on PF shall fail @@ -667,8 +667,8= @@ Just change the ADQ commands to MAC-VLAN :: =20 Remove MAC-VLAN commands :: =20 - ip link del macvlan0 - ethtool -K enp24s0f0 l2-fwd-offload off + ip link del macvlan0 + ethtool -K enp24s0f0 l2-fwd-offload off =20 =20 TC23: When DCF mode enabled, PF can't set L2 forwarding @@ -688,8 +688,8 @= @ Just change the ADQ commands to MAC-VLAN :: =20 Remove MAC-VLAN commands :: =20 - ip link del macvlan0 - ethtool -K enp24s0f0 l2-fwd-offload off + ip link del macvlan0 + ethtool -K enp24s0f0 l2-fwd-offload off =20 =20 TC24: DCF and L2 forwarding can be enabled on different PF @@ -702,12 +702= ,12 @@ Similar to ADQ test TC21 =20 Just change the ADQ commands to MAC-VLAN :: =20 - ethtool -K enp24s0f0 l2-fwd-offload on - ip link add link macvlan0 link enp24s0f0 type macvlan + ethtool -K enp24s0f1 l2-fwd-offload on + ip link add link macvlan0 link enp24s0f1 type macvlan ifconfig macvlan0 192.168.1.111 ipconfig macvlan0 up =20 Remove MAC-VLAN commands :: =20 - ip link del macvlan0 - ethtool -K enp24s0f0 l2-fwd-offload off + ip link del macvlan0 + ethtool -K enp24s0f1 l2-fwd-offload off -- 2.21.0