From: "Jiang, YuX" <yux.jiang@intel.com>
To: "christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>, dev <dev@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>,
"yanghliu@redhat.com" <yanghliu@redhat.com>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: RE: 19.11.14 patches review and test
Date: Wed, 7 Dec 2022 10:26:39 +0000 [thread overview]
Message-ID: <BYAPR11MB27116D98C4D9C1CF31FED4DBFE1A9@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221128131653.1403352-1-christian.ehrhardt@canonical.com>
Hi All,
Update the test status for Intel part. DPDK19.11.14-rc1 validation test is almost finished, no critical issue is found, but find some new bugs for build and power management.
New defects for build: No fix yet.
https://bugs.dpdk.org/show_bug.cgi?id=1140
https://bugs.dpdk.org/show_bug.cgi?id=1141
https://bugs.dpdk.org/show_bug.cgi?id=1142
New defects for power management: also find on LTS20.11.7
Compilation error compiling dpdk with vm_power_manager sample app. -- Intel dev is under investigating.
Known defects for build: No fix yet.
https://bugs.dpdk.org/show_bug.cgi?id=912
https://bugs.dpdk.org/show_bug.cgi?id=985
https://bugs.dpdk.org/show_bug.cgi?id=991
https://bugs.dpdk.org/show_bug.cgi?id=1121
https://bugs.dpdk.org/show_bug.cgi?id=1064
# Basic Intel(R) NIC testing
* Build: cover the build test combination with latest GCC/Clang version and the popular OS revision such as Ubuntu20.04&22.04, Fedora36, RHEL8.4, etc.
- All test done. Lots of build issues have no fix, including new and known.
* PF&VF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- All test done. No new bug 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.
# 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
> -----Original Message-----
> From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com>
> Sent: Monday, November 28, 2022 9: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>;
> yanghliu@redhat.com; Peng, Yuan <yuan.peng@intel.com>; Chen, Zhaoyan
> <zhaoyan.chen@intel.com>
> Subject: 19.11.14 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 19.11.14.
>
> The planned date for the final release is Tue 12th December 2022.
>
> 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.14-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>
>
> ---
next prev parent reply other threads:[~2022-12-07 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 13:16 christian.ehrhardt
2022-12-07 10:26 ` Jiang, YuX [this message]
2022-12-13 11:34 ` Christian Ehrhardt
2022-12-09 9:46 ` YangHang Liu
2022-12-11 14:40 ` Ali Alnubani
2022-12-13 11:28 ` Christian Ehrhardt
2022-12-13 11:41 ` Christian Ehrhardt
2022-12-13 19:46 ` Ali Alnubani
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=BYAPR11MB27116D98C4D9C1CF31FED4DBFE1A9@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=thomas@monjalon.net \
--cc=yanghliu@redhat.com \
--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).