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 6D2DBA0547; Tue, 9 Feb 2021 09:12:05 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E67034014E; Tue, 9 Feb 2021 09:12:04 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id 32FBE40147 for ; Tue, 9 Feb 2021 09:12:02 +0100 (CET) IronPort-SDR: TUuI8Nc/5k3/NJ/AOtHPLgCsf8Cu6ZzH0SKGpt/EVD7X4YviWQen0qR/izrr1BJZ19mSBWYrFt sDygiX1ZuP8w== X-IronPort-AV: E=McAfee;i="6000,8403,9889"; a="160997721" X-IronPort-AV: E=Sophos;i="5.81,164,1610438400"; d="scan'208";a="160997721" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Feb 2021 00:12:01 -0800 IronPort-SDR: Kv0UxD+4XW8OHysc3AqOnpgyEO4FSBas3xf8UFdYJw9tuTjwrLmemlV16JmFxW8HPdxkXaGvsD 9hAwpvnS/Ltg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.81,164,1610438400"; d="scan'208";a="398708192" Received: from irsmsx604.ger.corp.intel.com ([163.33.146.137]) by orsmga007.jf.intel.com with ESMTP; 09 Feb 2021 00:12:00 -0800 Received: from shsmsx605.ccr.corp.intel.com (10.109.6.215) by IRSMSX604.ger.corp.intel.com (163.33.146.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 9 Feb 2021 08:11:58 +0000 Received: from shsmsx605.ccr.corp.intel.com ([10.109.6.215]) by SHSMSX605.ccr.corp.intel.com ([10.109.6.215]) with mapi id 15.01.2106.002; Tue, 9 Feb 2021 16:11:55 +0800 From: "Jiang, YuX" To: Thomas Monjalon , "dev (dev@dpdk.org)" CC: "Devlin, Michelle" , "Mcnamara, John" , "Yigit, Ferruh" Thread-Topic: [dpdk-dev] [dpdk-announce] release candidate 21.02-rc3 Thread-Index: AQHW+/2LKwjTjJcgb0CLaV6ewd4dU6pPFGZw Date: Tue, 9 Feb 2021 08:11:55 +0000 Message-ID: <8a317b8958854b6fbdf1af323345cf12@intel.com> References: <5305610.D7H1GXTtC2@thomas> In-Reply-To: <5305610.D7H1GXTtC2@thomas> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-version: 11.5.1.3 dlp-reaction: no-action dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.02-rc3 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" All, Update the test status for Intel part. Validation test are almost finished.= =20 =20 # Basic Intel(R) NIC testing * Build or compile: =20 *Build: cover the build test combination with latest GCC/Clang/ICC versio= n and the popular OS revision such as Ubuntu20.04, CentOS 8.3, CentOS Strea= m 8, etc. - All passed. *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20= .04 and CentOS 8.3.=20 - All passed. *PF(i40e, ixgbe and igb): test scenarios including RTE_FLOW/TSO/Jumboframe= /checksum offload/VLAN/VXLAN, etc.=20 - All test are done. Only 1 bug is found. 4 issues found in RC2 are fixed= in RC3.=20 =20 *VF(i40e, ixgbe and igb): test scenarios including VF-RTE_FLOW/TSO/Jumbofr= ame/checksum offload/VLAN/VXLAN, etc. - All passed except known issue. No new issues are found. =20 =20 *PF/VF(ICE): test scenarios including /Switch features/Package Management/= Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Share code update/Flexible D= escriptor, etc. - All test are done. No new issues are found. 4 issues about QinQ found o= n RC2 are fixed in RC3.=20 =20 * Intel NIC single core/NIC performance: test scenarios including PF/VF si= ngle core performance test, RFC2544 Zero packet loss performance test, etc. - All passed. The performance is consistent with RC2.=20 =20 * Power and IPsec:=20 * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/P= riority Base Frequency and so on.=20 - Not test yet. =20 * IPsec: No test due to there's no codes changes. =20 =20 # Basic cryptodev and virtio testing * Virtio: both function and performance test are covered. Such as PVP/Virt= io_loopback/virtio-user loopback/virtio-net VM2VM perf testing/VMAWARE ESXI= 7.0u1, etc. - All passed except known issue. 4 Virtio related issue are fixed in RC3. =20 * Cryptodev:=20 *Function test: test scenarios including Cryptodev API testing/CompressDe= v ISA-L/QAT/ZLIB PMD Testing/FIPS, etc. - All passed. *Performance test: test scenarios including Thoughput Performance /Crypto= dev Latency, etc. - The performance is consistent with RC2. Best regards, Jiang, Yu > -----Original Message----- > From: dev On Behalf Of Thomas Monjalon > Sent: Saturday, February 6, 2021 4:29 AM > To: announce@dpdk.org > Subject: [dpdk-dev] [dpdk-announce] release candidate 21.02-rc3 >=20 > A new DPDK release candidate is ready for testing: > https://git.dpdk.org/dpdk/tag/?id=3Dv21.02-rc3 >=20 > There are 80 new patches in this snapshot. >=20 > Release notes: > https://doc.dpdk.org/guides/rel_notes/release_21_02.html >=20 > Please test and report issues on bugs.dpdk.org. > You may share some release validation results by replying to this message= at > dev@dpdk.org. >=20 > The -rc4 should include only critical bug fixes, doc and tooling. >=20 > Please think about sharing your roadmap for DPDK 21.05. >=20 > Thank you everyone >=20