From: "Jiang, YuX" <yux.jiang@intel.com>
To: "christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
Ali Alnubani <alialnu@nvidia.com>,
"Walker, Benjamin" <benjamin.walker@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
"hariprasad.govindharajan@intel.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@monjalon.net>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: RE: 19.11.12 patches review and test
Date: Wed, 30 Mar 2022 11:04:04 +0000 [thread overview]
Message-ID: <BYAPR11MB2711A952D92FE5F37D2F0E2EFE1F9@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220321115516.3986382-1-christian.ehrhardt@canonical.com>
> -----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 <Abhishek.Marathe@microsoft.com>;
> Ali Alnubani <alialnu@nvidia.com>; Walker, Benjamin
> <benjamin.walker@intel.com>; David Christensen
> <drc@linux.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@monjalon.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 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 <christian.ehrhardt@canonical.com>
>
Update the test status for Intel part. DPDK19.11.12-rc1 test rate is 60%, totally find four defects as below:
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.
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 <vanshika.shukla@nxp.com>, no fix yet.
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.
# 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
next prev parent reply other threads:[~2022-03-30 11:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 11:55 christian.ehrhardt
2022-03-30 11:04 ` Jiang, YuX [this message]
2022-03-31 10:00 ` Christian Ehrhardt
2022-04-06 6:49 ` Christian Ehrhardt
2022-04-06 7:05 ` Jiang, YuX
2022-04-06 8:40 ` Christian Ehrhardt
2022-03-31 10:50 ` Christian Ehrhardt
2022-04-01 14:34 ` Kalesh Anakkur Purayil
2022-04-04 6:35 ` Christian Ehrhardt
2022-04-04 6:39 ` Christian Ehrhardt
2022-04-04 7:02 ` Ali Alnubani
2022-04-04 6:52 ` Ali Alnubani
2022-04-04 7:12 ` Christian Ehrhardt
2022-04-06 2:11 ` Pei Zhang
2022-04-06 6:45 ` Christian Ehrhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BYAPR11MB2711A952D92FE5F37D2F0E2EFE1F9@BYAPR11MB2711.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hariprasad.govindharajan@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=ktraynor@redhat.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).