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-rc1
Date: Thu, 28 Oct 2021 07:10:36 +0000	[thread overview]
Message-ID: <SJ0PR11MB5150780AD8ACBEEDEC187D5FFE869@SJ0PR11MB5150.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2318225.2c2R9pzSo5@thomas>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Tuesday, October 26, 2021 5:41 AM
> To: announce@dpdk.org
> Subject: [dpdk-dev] [dpdk-announce] release candidate 21.11-rc1
>
> A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v21.11-rc1
>
> There are 1171 new patches in this snapshot, big as expected.
>
> Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_21_11.html
>
> Highlights of 21.11-rc1:
> * General
>       - more than 512 MSI-X interrupts
>       - hugetlbfs subdirectories
>       - mempool flag for non-IO usages
>       - device class for DMA accelerators
>       - DMA drivers for Intel DSA and IOAT
> * Networking
>       - MTU handling rework
>       - get all MAC addresses of a port
>       - RSS based on L3/L4 checksum fields
>       - flow match on L2TPv2 and PPP
>       - flow flex parser for custom header
>       - control delivery of HW Rx metadata
>       - transfer flows API rework
>       - shared Rx queue
>       - Windows support of Intel e1000, ixgbe and iavf
>       - testpmd multi-process
>       - pcapng library and dumpcap tool
> * API/ABI
>       - API namespace improvements (mempool, mbuf, ethdev)
>       - API internals hidden (intr, ethdev, security, cryptodev, eventdev,
> cmdline)
>       - flags check for future ABI compatibility (memzone, mbuf, mempool)
>
> Please test and report issues on bugs.dpdk.org.
> DPDK 21.11-rc2 is expected in two weeks or less.
>
> Thank you everyone
>
Update the test status for Intel part. Till now dpdk21.11-rc1 test execution rate is 50%. No critical issue is found.
But one little high issue https://bugs.dpdk.org/show_bug.cgi?id=843 impacts cryptodev function and performance test.
Bad commit id is 8cb5d08db940a6b26f5c5ac03b49bac25e9a7022/Author: Harman Kalra <hkalra@marvell.com>. Please help to handle it.
# 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.
        *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20.04 and Fedora34.
                - All test done.
                - Find one bug: https://bugs.dpdk.org/show_bug.cgi?id=841 Marvell Dev has provided patch and Intel validation team verify passed.
                  Patch link: http://patchwork.dpdk.org/project/dpdk/patch/20211027131259.11775-1-ktejasree@marvell.com/
        * PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
                - Execution rate is 60%. No new issue is found yet.
        * VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
                - Execution rate is 60%.
                - One bug https://bugs.dpdk.org/show_bug.cgi?id=845 about "vm_hotplug: vf testpmd core dumped after executing "device_del dev1" in qemu" is found.
                        Bad commit id is commit c2bd9367e18f5b00c1a3c5eb281a512ef52c5dfd Author: Harman Kalra <hkalra@marvell.com>
        * 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 60%.
                - One bug about kni_autotest failed on Suse15.3. Trying to find bad commit id. Known issues, Intel dev is under investigating.
        * 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 60%.
                - One bug about nic single core performance drop 2% is found. Bad commit id is commit:  efc6f9104c80d39ec168/Author: Olivier Matz <olivier.matz@6wind.com>
        * 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.
                        - Not Start.
# 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.
                - Execution rate is 80%.
                - Two new bugs are found.
                        - One about VMware ESXI 7.0U3: failed to start port. Intel Dev is under investigating.
                        - One https://bugs.dpdk.org/show_bug.cgi?id=840 about "dpdk-pdump capture the pcap file content are wrong" is found.
                        Bad commit id: commit 10f726efe26c55805cf0bf6ca1b80e97b98eb724    //bad commit id Author: Stephen Hemminger <stephen@networkplumber.org>
        * Cryptodev:
                *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
                        - Execution rate is 60%
                        - Two new bugs are found.
                                - One https://bugs.dpdk.org/show_bug.cgi?id=843 about crypto performance tests for QAT are failing. Bad commit id is 8cb5d08db940a6b26f5c5ac03b49bac25e9a7022/Author: Harman Kalra <hkalra@marvell.com>
                                - One https://bugs.dpdk.org/show_bug.cgi?id=842 about FIP tests are failing. Bad commit id is commit f6849cdcc6ada2a8bc9b82e691eaab1aecf4952f Author: Akhil Goyal gakhil@marvell.com
                *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
                        - Execution rate is 10%. Most of performance test are blocked by Bug843.

  reply	other threads:[~2021-10-28  7:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 21:40 Thomas Monjalon
2021-10-28  7:10 ` Jiang, YuX [this message]
2021-11-01 11:53   ` Jiang, YuX
2021-11-05 21:51 ` Thinh Tran
2021-11-08 10:50 ` Pei Zhang

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=SJ0PR11MB5150780AD8ACBEEDEC187D5FFE869@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).