From: Luca Boccassi <luca.boccassi@gmail.com>
To: "Jiang, YuX" <yux.jiang@intel.com>
Cc: dev <dev@dpdk.org>, "Mcnamara, John" <john.mcnamara@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: 20.11.7 patches review and test
Date: Mon, 12 Dec 2022 20:01:03 +0000 [thread overview]
Message-ID: <CAMw=ZnTHEB3EQHM3iskVOUg5ymGy_xZ6Tw3UjZG3wTrw0BnHFA@mail.gmail.com> (raw)
In-Reply-To: <CAMw=ZnQFe1pGmPaoRtbswBr6y5ju4Quq5mQbTh2c53pjOYaGmg@mail.gmail.com>
On Fri, 9 Dec 2022 at 09:49, Luca Boccassi <luca.boccassi@gmail.com> wrote:
>
> Thank you!
>
> The two compilation issues have been fixed. Waiting on a resolution on
> the other two issues. Should they be considered blockers and delay the
> release, if a fix is not available by next week?
Hi,
Any update on these two issues found by Intel testing? Should I block
the release waiting for a resolution?
> On Wed, 7 Dec 2022 at 10:22, Jiang, YuX <yux.jiang@intel.com> wrote:
> >
> > Hi All,
> > Update the test status for Intel part. Till now dpdk20.11.7-rc1 validation test rate is 95%. No critical issue is found.
> > 2 new bugs are found, 1 new issue is under confirming by Intel Dev.
> > New bugs:
> > 1, Compilation error compiling dpdk with vm_power_manager sample app -- Intel dev is under investigating.
> > 2, vf_interrupt_pmd/nic_interrupt_VF_vfio_pci: l3fwd-power Wake up failed on X722 37d0
> > - Find on DPDK22.11, it has fix patch: https://patchwork.dpdk.org/project/dpdk/patch/20221117065726.277672-1-kaisenx.you@intel.com/
> > - Patch is not merged into main, its fix can be applied on LTS20.11.7-rc1 and tested passed.
> > 3, inline ipsec: test failed on LTS20.11.7 -- Intel validation owner and dev are under investigating.
> >
> > # Basic Intel(R) NIC testing
> > * Build & CFLAG compile: cover the build test combination with latest GCC/Clang version and the popular OS revision such as Ubuntu20.04, Fedora36, RHEL8.4, etc.
> > - All test done. One known bug: https://bugs.dpdk.org/show_bug.cgi?id=991 net/ena build failure with gcc 12, still no 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.
> > - One issue is under confirming.
> >
> > # 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.
> > - All test passed.
> > *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
> > - All test done.
> >
> > Best regards,
> > Yu Jiang
> >
> > > -----Original Message-----
> > > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > > Sent: Monday, November 28, 2022 6:53 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>;
> > > Yanghang Liu <yanghliu@redhat.com>; Peng, Yuan <yuan.peng@intel.com>;
> > > Chen, Zhaoyan <zhaoyan.chen@intel.com>
> > > Subject: 20.11.7 patches review and test
> > >
> > > Hi all,
> > >
> > > Here is a list of patches targeted for stable release 20.11.7.
> > >
> > > The planned date for the final release is the 12th of December.
> > >
> > > 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=v20.11.7-rc1
> > >
> > > These patches are located at branch 20.11 of dpdk-stable repo:
> > > https://dpdk.org/browse/dpdk-stable/
> > >
> > > Thanks.
> > >
> > > Luca Boccassi
> > >
> > > ---
next prev parent reply other threads:[~2022-12-12 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 10:52 luca.boccassi
2022-11-28 11:35 ` Morten Brørup
2022-11-28 11:55 ` Luca Boccassi
2022-11-28 12:07 ` Morten Brørup
2023-04-11 7:22 ` Morten Brørup
2023-04-11 9:58 ` Luca Boccassi
2022-12-07 10:21 ` Jiang, YuX
2022-12-09 9:24 ` YangHang Liu
2022-12-09 9:50 ` Luca Boccassi
2022-12-09 9:49 ` Luca Boccassi
2022-12-12 20:01 ` Luca Boccassi [this message]
2022-12-13 9:05 ` Jiang, YuX
2022-12-13 10:12 ` Luca Boccassi
2022-12-11 16:15 ` Ali Alnubani
2022-12-12 20:00 ` Luca Boccassi
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='CAMw=ZnTHEB3EQHM3iskVOUg5ymGy_xZ6Tw3UjZG3wTrw0BnHFA@mail.gmail.com' \
--to=luca.boccassi@gmail.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=qian.q.xu@intel.com \
--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).