DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jiang, YuX" <yux.jiang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"dev (dev@dpdk.org)" <dev@dpdk.org>
Cc: "Devlin, Michelle" <michelle.devlin@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: RE: [dpdk-dev] [dpdk-announce] release candidate 21.11-rc2
Date: Thu, 11 Nov 2021 08:25:55 +0000	[thread overview]
Message-ID: <SJ0PR11MB5150C3005E47BE2B0A334CBBFE949@SJ0PR11MB5150.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2415599.WskMzomRmS@thomas>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Tuesday, November 9, 2021 8:45 AM
> To: announce@dpdk.org
> Subject: [dpdk-dev] [dpdk-announce] release candidate 21.11-rc2
>
> A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v21.11-rc2
>
> There are 448 new patches in this snapshot.
>
> Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_21_11.html
>
> Highlights of 21.11-rc2:
>       - Toeplitz hash using Galois Fields New Instructions (GFNI)
>       - virtio RSS
>       - vhost power monitor wakeup
>       - Xilinx vDPA driver
>       - DMA drivers for HiSilicon and Marvell CNXK
>       - GPU device class library
>       - AddressSanitizer (ASan) integration for debug
>       - more API internals hidden (ip_frag, vDPA)
>
> Please test and report issues on bugs.dpdk.org.
> Some bugs found with ASan are tagged and can be found with this query:
>       https://bugs.dpdk.org/buglist.cgi?quicksearch=[asan]
>
> DPDK 21.11-rc3 is expected in one week or less.
>
> Thank you everyone
>
All,

Update the test status for Intel part. Till now dpdk21.11-rc2 test execution rate is 85%. No critical issue is found.
But has some about missing '_mm512_set_epi8' support build issues. Intel has already sent a fix:
Patch Link: https://patches.dpdk.org/project/dpdk/patch/20211109172456.147140-1-vladimir.medvedkin@intel.com/

# 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, Fedora34, RHEL8.4, etc.
                - All test done.
                - One bug about lib/librte_power.a.p build failed on OS Fedora35 with clang 13.0.0 is found.
                        - Has fix patch for litrte_power, verify patch but find new failure, report bugzilla for new failure about fslmc.
        *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20.04 and Fedora34.
                - All passed.
        * PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
                - Execution rate is 90%. No new issue is found.
                - One 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.
        * VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
                - Execution rate is 85%. No new issue is found.
                - Known issues: Intel dev is investigating.
                        b, ixgbe_vf_get_extra_queue_information/ test_enable_dcb: executing "port config 0 dcb vt on 4 pfc off" failed under testpmd: has fix patch, but verify failed.
        * PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Share code update/Flexible Descriptor, etc.
                - Execution rate is 90%.
                - Two bugs about dcf_qos, cvl_qinq, Intel dev is under investigating.
                - One bug about stats_checks/xstats_check_vf: 'clear port xstats all' cannot clear xstats of port, has fix and verify passed.
                        - Fix patch link: https://patches.dpdk.org/project/dpdk/patch/20211109103303.3892176-1-radu.nicolau@intel.com/
        * Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc.
                - Execution rate is 80%. 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.
                        - 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.
                        - Execution rate is 80%.
                        - One new bug about "cryptodev_qat_asym_autotest is resulting in segmentation fault" is found in 21.11rc2.
                *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
                        - Execution rate is 80%. No big performance drop.

  reply	other threads:[~2021-11-11  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  0:45 Thomas Monjalon
2021-11-11  8:25 ` Jiang, YuX [this message]
2021-11-11  8:57   ` David Marchand
2021-11-16  7:13   ` Jiang, YuX
2021-11-15  4:34 ` Pei Zhang
2021-11-15  5:00 ` [dpdk-dev] " Kalesh Anakkur Purayil
2021-11-17 19:56 ` Thinh Tran

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=SJ0PR11MB5150C3005E47BE2B0A334CBBFE949@SJ0PR11MB5150.namprd11.prod.outlook.com \
    --to=yux.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=michelle.devlin@intel.com \
    --cc=thomas@monjalon.net \
    /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).