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 84F75A0509; Wed, 6 Apr 2022 08:49:52 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1C46140E2D; Wed, 6 Apr 2022 08:49:52 +0200 (CEST) Received: from smtp-relay-internal-1.canonical.com (smtp-relay-internal-1.canonical.com [185.125.188.123]) by mails.dpdk.org (Postfix) with ESMTP id 333F740DF6 for ; Wed, 6 Apr 2022 08:49:50 +0200 (CEST) Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id CD64D3F7F8 for ; Wed, 6 Apr 2022 06:49:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1649227789; bh=fK60Bj4nu788efPWU2SjDjLVgcIH+O+gujbud/qNwc0=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=oMy9ygmddyb6uxT+PAqg5GbDA9USCybH+3GjcZNS30ir1eeAfxIGong0gqytPtqh+ yKM07XqR4PzDmrC6XB8Ce3SpblRliK/n/rW2Ph9tsX92IdiaT9RtOBnulfekbNkhs+ jv7yxJOhPABzhXn8Hled+E0OseS4N6hNUuK95m3ruARDQhEGjA2G6aP8tTwFQe91UC Dr3noDx9mcDgwN65AazkD0452DQu+W4c6hRbrTtP+E0TRzTjnQOCEYfPwEeNZRcHmJ n7kwJr7qqd1omtglG6QhFispeU9riths0raQ+g8Kh2U4lg1qyCm5++BVC9+bAUOqRq 5kJKaTc3svvsw== Received: by mail-qv1-f72.google.com with SMTP id w10-20020a05621412ea00b00440d10d2799so2393889qvv.9 for ; Tue, 05 Apr 2022 23:49:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fK60Bj4nu788efPWU2SjDjLVgcIH+O+gujbud/qNwc0=; b=7Z0yizFBc4u2lvO1bBMthwSLLNyRtdGvQnysGCm0nUkxkPCZ6P5iGRoOULXcm82KC4 BO6Ak05kLKp0fRFAh8XZHOn0kfAPbHfdV1lS8kv5HpeBPLTZBperzbUqVvCed1InHOvj AH7zzjkMVfj1bHXaM7VLWZgN8ctz7+M2PeC9wpHq7R6bL40smSPuy+rebdPwN5uJDdaZ r0RdAzf2HBvuyI9rBrZ7/iGifu2ixSTjqS8VlGx3W9fCtIiMQIsV3cG/Go9oyaMiQPtq Gh1jJ7nxCtwgxr57AM9ExdxK+FYtb6R7E4m1h/x9i9G9TY2s9A89CWE2JuJH8C9++nbH RDAw== X-Gm-Message-State: AOAM533AjuKmvIWblje4kzamoI2FwtMxicTfGCuvz6S4QSA+4wEXWBTu K9pINtCyTfl2jQyy/cPQyfRxS+jlUZ9YdrqyJ8k6Ql2FqRIDuO08YKdXpBoGX+Z8rUe7FqWr+0K pkAAaxJrlIgaKdSyuYV3zmD5XHsdk2CMO9kvm X-Received: by 2002:a05:6214:2b07:b0:432:f7e6:e443 with SMTP id jx7-20020a0562142b0700b00432f7e6e443mr6086984qvb.125.1649227788901; Tue, 05 Apr 2022 23:49:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxgUP/BaP0+0xShtDojyG+tYZ0elGipKSG6X45fcfLicVRPhubSs21Kxw3+MC9jSgWW0QsuZub4yc4oYuu9T/M= X-Received: by 2002:a05:6214:2b07:b0:432:f7e6:e443 with SMTP id jx7-20020a0562142b0700b00432f7e6e443mr6086964qvb.125.1649227788698; Tue, 05 Apr 2022 23:49:48 -0700 (PDT) MIME-Version: 1.0 References: <20220321115516.3986382-1-christian.ehrhardt@canonical.com> In-Reply-To: From: Christian Ehrhardt Date: Wed, 6 Apr 2022 08:49:22 +0200 Message-ID: Subject: Re: 19.11.12 patches review and test To: "Jiang, YuX" Cc: "stable@dpdk.org" , "dev@dpdk.org" , Abhishek Marathe , Ali Alnubani , "Walker, Benjamin" , David Christensen , "hariprasad.govindharajan@intel.com" , Hemant Agrawal , "Stokes, Ian" , Jerin Jacob , "Mcnamara, John" , Ju-Hyoung Lee , Kevin Traynor , Luca Boccassi , Pei Zhang , "Xu, Qian Q" , Raslan Darawsheh , Thomas Monjalon , "Peng, Yuan" , "Chen, Zhaoyan" Content-Type: multipart/alternative; boundary="0000000000007fd76405dbf6c428" 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 --0000000000007fd76405dbf6c428 Content-Type: text/plain; charset="UTF-8" On Thu, Mar 31, 2022 at 12:00 PM Christian Ehrhardt < christian.ehrhardt@canonical.com> wrote: > > > On Wed, Mar 30, 2022 at 1:04 PM Jiang, YuX wrote: > >> > -----Original Message----- >> > From: christian.ehrhardt@canonical.com < >> christian.ehrhardt@canonical.com> >> > Sent: Monday, March 21, 2022 7:55 PM >> > To: stable@dpdk.org >> > Cc: dev@dpdk.org; Abhishek Marathe ; >> > Ali Alnubani ; Walker, Benjamin >> > ; David Christensen >> > ; hariprasad.govindharajan@intel.com; Hemant >> > Agrawal ; Stokes, Ian ; >> > Jerin Jacob ; Mcnamara, John >> > ; Ju-Hyoung Lee ; >> > Kevin Traynor ; Luca Boccassi ; >> > Pei Zhang ; Xu, Qian Q ; >> > Raslan Darawsheh ; Thomas Monjalon >> > ; Peng, Yuan ; Chen, >> > Zhaoyan >> > Subject: 19.11.12 patches review and test >> > >> > Hi all, >> > >> > Here is a list of patches targeted for stable release 19.11.12. >> > >> > The planned date for the final release is 7th of April. >> > >> > Please help with testing and validation of your use cases and report any >> > issues/results with reply-all to this mail. For the final release the >> fixes and >> > reported validations will be added to the release notes. >> > >> > A release candidate tarball can be found at: >> > >> > https://dpdk.org/browse/dpdk-stable/tag/?id=v19.11.12-rc1 >> > >> > These patches are located at branch 19.11 of dpdk-stable repo: >> > https://dpdk.org/browse/dpdk-stable/ >> > >> > Thanks. >> > >> > Christian Ehrhardt >> > >> Update the test status for Intel part. DPDK19.11.12-rc1 test rate is 60%, >> totally find four defects as below: >> > > Thank you for all your work! > > >> Bug1:[dpdk-19.11.12] metering_and_policing/ipv4_HASH_table_RFC2698: >> unable to forward packets normally. Intel Dev is investigating. >> Bug2:[LTS DPDK-19.11.12-rc1] cryptodev_qat_asym_autotest is failing. >> Intel Dev is investigating. >> > > Both are very interesting, could you make sure that by next Wednesday (6th > of April) there is feedback on this thread if this is either: > Hi Jiang YuX, by now everything else is in place to tag the 19.11.12 release tomorrow, therefore I wanted to ping for these updates so that we can make the right decision to release or delay. > 1. fixable, with a pointer to a fix > 2. not fixed yet, but also not too bad (or not a regression to the former > state) and thereby does not block 19.11.12 > 3. not fixed yet, but being very severe blocking 19.11.12, but identified > the offending commit that shall be reverted > 4. not fixed yet, but being very severe blocking 19.11.12, and an ETA of a > fix/mitigation > > Based on that outcome we then need to decide if we need to tag -rc2 and > another round of verifications. > > Bug3:https://bugs.dpdk.org/show_bug.cgi?id=978 [dpdk-19.11.12-rc1] >> drivers/net/qede make build failed on Fedora35 with Clang13.0.0. >> > Bad commit from Vanshika Shukla , no fix yet. >> > > Thanks for identifying this one. > As in the past, we are willing to take build time fixes for newer compiler > stacks, but we are not blocked on releasing 19.11.12 unless platforms > formerly building and using it are affected. > > >> Bug4:https://bugs.dpdk.org/show_bug.cgi?id=977 [dpdk-19.11.12-rc1] >> bnxt_stats meson&&make build Error on Fedora35-64 and Ubuntu2110-64 with >> gcc11.2.1&&gcc11.2.0. >> > Has fix ( >> https://github.com/cpaelzer/dpdk-stable-queue/commit/f17a5eb33a2fec2f33476743f56d1fb2d37ca3b7.patch) >> and verify passed. >> > > Yes thanks, this one is indeed already applied > > >> >> # Basic Intel(R) NIC testing >> * Build: cover the build test combination with latest GCC/Clang/ICC >> version and the popular OS revision such as Ubuntu20.04, Fedora35, RHEL8.4, >> etc. >> - All test done. Two new bugs are found, and one known bug( >> https://bugs.dpdk.org/show_bug.cgi?id=747) >> * PF(i40e, ixgbe): test scenarios including >> RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. >> - Execution rate is 30%, no new issue is found. >> * VF(i40e, ixgbe): test scenarios including >> VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. >> - Execution rate is 30%, no new issue is found. >> * PF/VF(ice): test scenarios including Switch features/Package >> Management/Flow Director/Advanced Tx, etc. >> - All test done. No new issue is found. >> * Intel NIC single core/NIC performance: test scenarios including PF/VF >> single core performance test etc. >> - All test done. No big performance drop. >> * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test >> - QAT&SW/FIB library, etc. >> - On going. >> # Basic cryptodev and virtio testing >> * Virtio: both function and performance test are covered. Such as >> PVP/Virtio_loopback/virtio-user loopback/virtio-net VM2VM perf testing, etc. >> - All test done. No new issue is found. >> * Cryptodev: >> * Function test: test scenarios including Cryptodev API >> testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/ etc. >> - On going. >> * Performance test: test scenarios including Thoughput Performance >> /Cryptodev Latency, etc. >> - On going. >> >> BRs >> Yu Jiang >> > > > -- > Christian Ehrhardt > Staff Engineer, Ubuntu Server > Canonical Ltd > -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd --0000000000007fd76405dbf6c428 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Mar 31, 2022 at 12:00 PM Chri= stian Ehrhardt <chri= stian.ehrhardt@canonical.com> wrote:

On Wed, M= ar 30, 2022 at 1:04 PM Jiang, YuX <yux.jiang@intel.com> wrote:
> -----Original Message-----
> From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com<= /a>>
> Sent: Monday, March 21, 2022 7:55 PM
> To: stable@dpdk.o= rg
> Cc: dev@dpdk.org= ; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Ali Alnubani <alialnu@nvidia.com>; Walker, Benjamin
> <ben= jamin.walker@intel.com>; David Christensen
> <drc@li= nux.vnet.ibm.com>; hariprasad.govindharajan@intel.com; Hemant
> Agrawal <hemant.agrawal@nxp.com>; Stokes, Ian <ian.stokes@intel.com>;
> Jerin Jacob <jerinj@marvell.com>; Mcnamara, John
> <john.= mcnamara@intel.com>; Ju-Hyoung Lee <juhlee@microsoft.com>;
> Kevin Traynor <ktraynor@redhat.com>; Luca Boccassi <bluca@debian.org>;
> Pei Zhang <= pezhang@redhat.com>; Xu, Qian Q <qian.q.xu@intel.com>;
> Raslan Darawsheh <rasland@nvidia.com>; Thomas Monjalon
> <thomas@mo= njalon.net>; Peng, Yuan <yuan.peng@intel.com>; Chen,
> Zhaoyan <zhaoyan.chen@intel.com>
> Subject: 19.11.12 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 19.11.12.
>
> The planned date for the final release is 7th of April.
>
> Please help with testing and validation of your use cases and report a= ny
> issues/results with reply-all to this mail. For the final release the = fixes and
> reported validations will be added to the release notes.
>
> A release candidate tarball can be found at:
>
>=C2=A0 =C2=A0 =C2=A0https://dpdk.org/= browse/dpdk-stable/tag/?id=3Dv19.11.12-rc1
>
> These patches are located at branch 19.11 of dpdk-stable repo:
>=C2=A0 =C2=A0 =C2=A0https://dpdk.org/browse/dpdk-stable/=
>
> Thanks.
>
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
Update the test status for Intel part. DPDK19.11.12-rc1 test rate is 60%, t= otally find four defects as below:

Than= k you for all your work!
=C2=A0
Bug1:[dpdk-19.11.12] metering_and_policing/ipv4_HASH_table_RFC2698: unable = to forward packets normally. Intel Dev is investigating.
Bug2:[LTS DPDK-19.11.12-rc1] cryptodev_qat_asym_autotest is failing. Intel = Dev is investigating.

Both are very int= eresting, could you make sure that by next Wednesday (6th of April) there i= s feedback on this thread if this is either:
=

Hi=C2=A0Jiang YuX,
by now everything else is = in place to tag the 19.11.12 release tomorrow,
therefore I wanted= to ping for these updates so that we can make the right decision to releas= e or delay.
=C2=A0
1. fixable, wit= h a pointer to a fix
2. not fixed yet, but also not too bad (or n= ot a regression to the former state) and thereby does not block 19.11.12
3. not fixed yet, but being very severe blocking 19.11.12, but iden= tified the offending=C2=A0commit that shall be reverted
4. no= t fixed yet, but being very severe blocking 19.11.12, and an ETA of a fix/m= itigation

Based on that outcome we then need to de= cide if we need to tag -rc2 and another round of verifications.
<= br>
Bug3:https://bugs.dpdk.org/show_bug.cgi?id=3D978 [dpd= k-19.11.12-rc1] drivers/net/qede make build failed on Fedora35 with Clang13= .0.0.
> Bad commit from Vanshika Shukla <vanshika.shukla@nxp.com>, no fix yet.
=

Thanks for identifying this one.
As in the past, we are willing to take build time fixes for newer compiler= stacks, but we are not blocked on releasing 19.11.12 unless platforms form= erly building and using it are affected.
=C2=A0
Bug4:https://bugs.dpdk.org/show_bug.cgi?id=3D977 [dpd= k-19.11.12-rc1] bnxt_stats meson&&make build Error on Fedora35-64 a= nd Ubuntu2110-64 with gcc11.2.1&&gcc11.2.0.
> Has fix (https://github.com/cpaelzer/dpdk-stable-queue/commit/f17a5eb33= a2fec2f33476743f56d1fb2d37ca3b7.patch) and verify passed.

Yes thanks, this one is indeed already applied
=
=C2=A0

# Basic Intel(R) NIC testing
* Build: cover the build test combination with latest GCC/Clang/ICC version= and the popular OS revision such as Ubuntu20.04, Fedora35, RHEL8.4, etc. - All test done. Two new bugs are found, and one known bug(https://bugs.dpdk.org/show_bug.cgi?id=3D747)
* PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksu= m offload/VLAN/VXLAN, etc.
- Execution rate is 30%, no new issue is found.
* VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/chec= ksum offload/VLAN/VXLAN, etc.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0
- Execution rate is 30%, no new issue is found.
* PF/VF(ice): test scenarios including Switch features/Package Management/F= low Director/Advanced Tx, etc.
- All test done. No new issue is found.
* Intel NIC single core/NIC performance: test scenarios including PF/VF sin= gle core performance test etc.
- All test done. No big performance drop.
* IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test -= QAT&SW/FIB library, etc.
- On going.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0
# Basic cryptodev and virtio testing
* Virtio: both function and performance test are covered. Such as PVP/Virti= o_loopback/virtio-user loopback/virtio-net VM2VM perf testing, etc.
- All test done. No new issue is found.
* Cryptodev:
* Function test: test scenarios including Cryptodev API testing/CompressDev= ISA-L/QAT/ZLIB PMD Testing/ etc.
- On going.
* Performance test: test scenarios including Thoughput Performance /Cryptod= ev Latency, etc.
- On going.

BRs
Yu Jiang


--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
=


--
Christian Ehrhardt
Staff Engineer, Ubuntu Ser= ver
Canonical Ltd
--0000000000007fd76405dbf6c428--