From: David Marchand <david.marchand@redhat.com>
To: "Jiang, YuX" <yux.jiang@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev <dev@dpdk.org>,
"Devlin, Michelle" <michelle.devlin@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: release candidate 21.11-rc4
Date: Fri, 26 Nov 2021 14:09:44 +0100 [thread overview]
Message-ID: <CAJFAV8wASNiSiJD3_WPxb0DAid-Q8_o9f_Gr5vjiGOZ1kWt1Mw@mail.gmail.com> (raw)
In-Reply-To: <BN9PR11MB5530CF831E662101B76DB91BFE639@BN9PR11MB5530.namprd11.prod.outlook.com>
On Fri, Nov 26, 2021 at 12:47 PM Jiang, YuX <yux.jiang@intel.com> wrote:
> > You may share some release validation results by replying to this message at
> > dev@dpdk.org.
>
> Update the test status for Intel part. Till now dpdk21.11-rc4 validation test is almost finished. No critical issue and no new issue is found.
> # Basic Intel(R) NIC testing
> * Build or compile:
> *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.
> - Known bug: https://bugs.dpdk.org/show_bug.cgi?id=881: dpdk-next-net-mrvl branch still need rebase the fix.
> *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20.04 and RHEL8.4.
> - All passed.
> * PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> - All test done. No new issue is found.
> - One known bug https://bugs.dpdk.org/show_bug.cgi?id=864: pmd_stacked_bonded/test_mode_backup_rx:after setup stacked bonded ports,start top level bond port.
> - still verify failed based on dpdk21.11-rc4.
> * VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> - All test done. No new issue is found.
> - Two known bugs. Intel dev is investigating them.
> [dpdk-21.11]vf_jumboframe/test_vf_jumbo_withjumbo: launch testpmd failed on driver ixgbe-5.13.4
> [dpdk-21.11]vf_vlan/add_pvid_vf: launch testpmd showing error log after vf vlan in kernel pf
> * PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Share code update/Flexible Descriptor, etc.
> - All test done. No new issue is found.
> * Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc.
> - All test done. No big performance drop.
> * Power and IPsec:
> * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, etc.
> - All passed.
> * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
> - Most have done, all 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.
> - Known issue:
> - One about VMware ESXI 7.0U3: failed to start port. Intel Dev is under investigating.
> * Cryptodev:
> *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
> - All test done. No new issue is found.
> *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
> - All test done. No big performance drop.
Thanks for the report!
--
David Marchand
prev parent reply other threads:[~2021-11-26 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 18:38 David Marchand
2021-11-25 16:08 ` Stokes, Ian
2021-11-26 10:09 ` David Marchand
[not found] ` <PAXPR04MB94450A1D2DA550950C0E2FD6EF639@PAXPR04MB9445.eurprd04.prod.outlook.com>
2021-11-26 10:10 ` [EXT] " David Marchand
2021-11-26 11:47 ` Jiang, YuX
2021-11-26 13:09 ` David Marchand [this message]
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=CAJFAV8wASNiSiJD3_WPxb0DAid-Q8_o9f_Gr5vjiGOZ1kWt1Mw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=michelle.devlin@intel.com \
--cc=thomas@monjalon.net \
--cc=yux.jiang@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).