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 1572EA04FF; Thu, 31 Mar 2022 12:01:18 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E921C40DF6; Thu, 31 Mar 2022 12:01:17 +0200 (CEST) Received: from smtp-relay-internal-0.canonical.com (smtp-relay-internal-0.canonical.com [185.125.188.122]) by mails.dpdk.org (Postfix) with ESMTP id 4D2D240DF6 for ; Thu, 31 Mar 2022 12:01:17 +0200 (CEST) Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) (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-0.canonical.com (Postfix) with ESMTPS id 12D5A3F806 for ; Thu, 31 Mar 2022 10:01:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1648720877; bh=u0jER7bQXoSvnD98hdR3zvP9+sp+0gv92HBsxl8ksh0=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=fqc/+FLXEmaH/+1qNEOj5TUO3wqqZB+DiIjqn1PDNlssQEtJOIm5ZJ8cV45//Tto8 SmYSqWRcjj8g69vz4Rfd12VX9udMQllZWw1tMFlN44KTlFBWcDj7Ps48mW+GALS8Br F0nNn4/OXk6xsKxt/jZ3XfAKpNv0z7th4OsGg/F2hJ1Pjj8cPbHLRd4HySyKKhN8A1 0KFYCPNR+42j9dEWeyg7+UgYYE6XyagF+rdwN3GSz7Cx92Zn0TBrwLwlKHg0i8eMvN Y7ChylmUFjMDGWBUzQWeFtLpHDBzcd2CBNbk1g+PHMiQzqoshEQEkwdZr7R5JHBD08 BJD8HK3AW1Myw== Received: by mail-qt1-f198.google.com with SMTP id e5-20020ac85985000000b002e217abd72fso19683140qte.9 for ; Thu, 31 Mar 2022 03:01:17 -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=u0jER7bQXoSvnD98hdR3zvP9+sp+0gv92HBsxl8ksh0=; b=pRK3gpRH3ggBf5JJ1LQKNnZon6jM1KE/mX/N6NAppG4NIDGBzvlcCuqEBL/bPbL+FW jVDl/KBvFxEEo5IxBjCtkxtYbzXcLp554l+Ft18y245wwHYCIIVeG6ASL8NKCInHf+N4 AXzd2c+GEzOMGnTGKzF1kL5AENm/upxs8vpDCS5dc9D92XpxMPYdchgSTzfx8IkB+MKh XqsDgf4ig2uyncIx0eot/vcvfIOkKQYzGpnt9JGivFI5erx9enfgxp+YaqZhpNwYtYnC VrSxHbUBb40RagmBjXP/2Wvh7N3h53yDxBAeNZIkFWH2oj1dUz79m3DQDDSa1OtZpWdR XlKQ== X-Gm-Message-State: AOAM533gQg9bqz21aBoqdQ6OjMkGi0CgJS9iJca6CB4e2TT4DO35zGqh awZz2runIz/RYOQCe2Y2qwboCygnhjByloKSYavW8po1YL9UGURyuYXbYPRqI3DEy9PocW0i6x+ JUweCyUKLkHX5dp+Fv+Xcq0XRceqptZwV+rnf X-Received: by 2002:ac8:5c45:0:b0:2e1:9144:2849 with SMTP id j5-20020ac85c45000000b002e191442849mr3433082qtj.510.1648720876145; Thu, 31 Mar 2022 03:01:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyiGKQWiS8mTAQ2qMCctYwqT6YPHNfH7eemdrDrSZ3aL1SmxThiE0EH1RM38E3TobeDKKv0pRuzaNjxWq2T220= X-Received: by 2002:ac8:5c45:0:b0:2e1:9144:2849 with SMTP id j5-20020ac85c45000000b002e191442849mr3433027qtj.510.1648720875658; Thu, 31 Mar 2022 03:01:15 -0700 (PDT) MIME-Version: 1.0 References: <20220321115516.3986382-1-christian.ehrhardt@canonical.com> In-Reply-To: From: Christian Ehrhardt Date: Thu, 31 Mar 2022 12:00:49 +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="00000000000020b36605db80be4e" 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 --00000000000020b36605db80be4e Content-Type: text/plain; charset="UTF-8" On Wed, Mar 30, 2022 at 1:04 PM Jiang, YuX wrote: > > -----Original Message----- > > From: 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: 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 --00000000000020b36605db80be4e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Mar 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:
1. fixable, with a p= ointer 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 identifie= d the offending=C2=A0commit that shall be reverted
4. not fix= ed yet, but being very severe blocking 19.11.12, and an ETA of a fix/mitiga= tion

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=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 Ser= ver
Canonical Ltd
--00000000000020b36605db80be4e--