From: Kevin Traynor <ktraynor@redhat.com>
To: "Jiang, YuX" <yux.jiang@intel.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>,
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: 21.11.1 patches review and test
Date: Wed, 13 Apr 2022 14:19:39 +0100 [thread overview]
Message-ID: <df77e31c-f507-ac12-4c8e-5219939a1b06@redhat.com> (raw)
In-Reply-To: <BYAPR11MB2711306DA6DF0A7A40095E7AFEED9@BYAPR11MB2711.namprd11.prod.outlook.com>
On 12/04/2022 09:58, Jiang, YuX wrote:
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Friday, April 1, 2022 6:22 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: 21.11.1 patches review and test
>>
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.1.
>>
>> Please try and complete validation by April 13th.
>>
>> 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=v21.11.1-rc1
>>
>> These patches are located at branch 21.11 of dpdk-stable repo:
>> https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin
>>
>> ---
>
> Update the test status for Intel part. Till now dpdk21.11.1-rc1 test rate is 90%. Till now, no critical issue is found.
> Failure defect:
> Bug1: https://bugs.dpdk.org/show_bug.cgi?id=992 [dpdk 21.11.1-rc1] drivers/net/cnxk/cnxk_ethdev_mtr meson build failed with cflag param optimization=1 on Ubuntu20.04 with GCC10.3
> > It was found in 22.03-rc2(https://bugs.dpdk.org/show_bug.cgi?id=939), validation team apply 939's patch failed. Need new patch for LTS21.11.1-rc1.
>
Thanks for reporting this. I couldn't reproduce but sent a patch and
updated the Bz. Please try it out if you can.
Kevin.
> # Basic Intel(R) NIC testing
> * Build&CFLAG compile: 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. Find new bug: Bug1, not fix.
> * PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> - All test done. No new dpdk issue is found.
> * VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> - All test done. No new dpdk issue is found.
> * PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.
> - All test done. No new dpdk 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.
> - All test passed.
> * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, etc.
> - All test passed.
>
> # 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/VMAWARE ESXI 7.0u3, 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/FIPS, etc.
> - Test rate: 80%, no new issue is found currently.
> *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
> - Test rate: 80%, no new issue is found currently.
>
> BRs
> Yu Jiang
next prev parent reply other threads:[~2022-04-13 13:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 10:22 Kevin Traynor
2022-04-11 3:03 ` Pei Zhang
2022-04-13 4:06 ` YangHang Liu
2022-04-13 13:20 ` Kevin Traynor
2022-04-11 6:58 ` Christian Ehrhardt
2022-04-13 7:26 ` Christian Ehrhardt
2022-04-13 8:44 ` Kevin Traynor
2022-04-13 10:06 ` Kevin Traynor
2022-04-14 5:52 ` Christian Ehrhardt
2022-04-14 7:17 ` Thomas Monjalon
2022-04-14 9:08 ` Kevin Traynor
2022-04-11 11:00 ` Ali Alnubani
2022-04-13 13:18 ` Kevin Traynor
2022-04-12 8:58 ` Jiang, YuX
2022-04-13 13:19 ` Kevin Traynor [this message]
2022-04-14 4:58 ` Jiang, YuX
2022-04-25 15:01 ` Kevin Traynor
2022-04-20 5:50 ` Christian Ehrhardt
2022-04-25 13:39 ` Kevin Traynor
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=df77e31c-f507-ac12-4c8e-5219939a1b06@redhat.com \
--to=ktraynor@redhat.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--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=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=yux.jiang@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).