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>,
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.13 patches review and test
Date: Fri, 29 Jul 2022 12:08:03 +0000 [thread overview]
Message-ID: <BYAPR11MB2711C4E17B7E83F1AB71404AFE999@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220718101721.2993978-1-christian.ehrhardt@canonical.com>
> -----Original Message-----
> From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com>
> Sent: Monday, July 18, 2022 6:17 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>; 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.13 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 19.11.13.
>
> The planned date for the final release is August 29th.
>
> 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.13-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.13-rc1 almost test finished, no critical issue is found, but find some new bugs on new OS.
New report defects:
Bug1: https://bugs.dpdk.org/show_bug.cgi?id=1056 [dpdk-19.11.13-rc1] unit_tests_eal/link_bonding_rssconf: link_bonding_rssconf_autotest test failed
> This is found in 22.07, but that fix failed to be applied to LTS19.11, need rebase.
Build-Bug2: [dpdk 19.11.13-rc1] lib/librte_eal meson build error with gcc12.1 on fedora36, similar as https://bugs.dpdk.org/show_bug.cgi?id=985
> No fix yet.
Build-Bug3: [dpdk 19.11.13-rc1] drivers/net/ena make build error with gcc12.1 on fedora36, similar as https://bugs.dpdk.org/show_bug.cgi?id=991
> No fix yet.
Build-Bug4: [dpdk 19.11.13-rc1] drivers/net/ice/ice_rxtx meson build error with gcc11.2 on Ubuntu22.04".
> This is found in 22.07, but that fix failed to be applied to LTS19.11, need rebase, Intel Dev is under investigating.
Build-Bug5: [dpdk 19.11.13-rc1] /lib/eal meson and make build failed with gcc10.3.0 and clang13.0.0 on FreeBSD13.1/64.
> This is found in 22.07, but that fix failed to be applied to LTS19.11, need rebase, Intel Dev(Bruce) has send fix.
Build-Bug6: [dpdk 19.11.13-rc1] drivers/net/qede make build error with clang14 on fedora36/redhat8.6/UB22.04
> Known issue, https://bugs.dpdk.org/show_bug.cgi?id=912, no fix yet.
# 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&22.04, Fedora36, RHEL8.4, etc.
- All test done.
* PF&VF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- All test done. Find one new bug: Bug1.
* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx, etc.
- All test done. No new issue is found. Known bug about [dpdk-19.11.12] metering_and_policing/ipv4_HASH_table_RFC2698: unable to forward packets normally. Intel Dev is still investigating.
* 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.
# 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.
- All test done. No new issue is found.
* Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
- All test done. No performance drop.
Best regards,
Yu Jiang
next prev parent reply other threads:[~2022-07-29 12:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 10:17 christian.ehrhardt
2022-07-19 2:43 ` Pei Zhang
2022-07-19 5:27 ` Christian Ehrhardt
2022-08-03 4:39 ` YangHang Liu
2022-08-03 10:19 ` Christian Ehrhardt
2022-07-29 12:08 ` Jiang, YuX [this message]
2022-08-03 10:19 ` Christian Ehrhardt
2022-08-03 10:29 christian.ehrhardt
2022-08-04 8:21 christian.ehrhardt
2022-08-11 7:37 ` Jiang, YuX
2022-08-11 7:50 ` Christian Ehrhardt
2022-08-18 16:11 ` Ali Alnubani
2022-08-19 5:32 ` YangHang Liu
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=BYAPR11MB2711C4E17B7E83F1AB71404AFE999@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=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).