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>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: RE: release candidate 22.11-rc3
Date: Thu, 17 Nov 2022 08:48:51 +0000	[thread overview]
Message-ID: <BYAPR11MB27112F2A4F245E9349A9AAC6FE069@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1720725.X513TT2pbd@thomas>

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, November 16, 2022 1:33 AM
> To: announce@dpdk.org
> Subject: release candidate 22.11-rc3
>
> A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v22.11-rc3
>
> There are 161 new patches in this snapshot.
>
> Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_22_11.html
>
> Please test and report issues on bugs.dpdk.org.
> You may share some release validation results by replying to this message at
> dev@dpdk.org and by adding tested hardware in the release notes.
>
> DPDK 22.11-rc4 should be the last chance for bug fixes and doc updates, and it
> is planned for the end of this week.
>
> Thank you everyone
>

Update the test status for Intel part. Till now dpdk22.11-rc3 test execution rate is 65%.
One new critical issue is found, hope it can be fixed in 22.11.
  https://bugs.dpdk.org/show_bug.cgi?id=1128 [dpdk22.11-rc3]failed to start testpmd with the mbuf-size parameter
  bad commit id:
  commit 4f04edcda769770881832f8036fd209e7bb6ab9a
        Author: Hanumanth Pothula <hpothula@marvell.com>
        Date:   Thu Nov 10 15:46:31 2022 +0530

                app/testpmd: support multiple mbuf pools per Rx queue

                Some of the HW has support for choosing memory pools based on
                the packet's size. The pool sort capability allows PMD/NIC to
                choose a memory pool based on the packet's length.

                On multiple mempool support enabled, populate mempool array
                accordingly. Also, print pool name on which packet is received.

                Signed-off-by: Hanumanth Pothula <hpothula@marvell.com>
                Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>

Find one new bug about "[DPDK22.11] idpf: failed to start port all", Intel dev has provided fix patch, and validation team verify passed, hope it can be merged into RC4.
  - patch link: https://patches.dpdk.org/project/dpdk/patch/20221117030744.45460-1-beilei.xing@intel.com/

Meson test known bugs:
  1, https://bugs.dpdk.org/show_bug.cgi?id=1107 [22.11-rc1][meson test] seqlock_autotest test failed, which is only found on CentOS7.9/gcc4.8.5. No fix yet.
  2, https://bugs.dpdk.org/show_bug.cgi?id=1024 [dpdk-22.07][meson test] driver-tests/link_bonding_mode4_autotest bond handshake failed. No fix yet.
Asan test known bugs:
  https://bugs.dpdk.org/show_bug.cgi?id=1123 [dpdk-22.11][asan] the stack-buffer-overflow was found when quit testpmd in Redhat9. No fix yet.

# Basic Intel(R) NIC testing
* Build or compile:
 *Build: cover the build test combination with latest GCC/Clang version and the popular OS revision such as Ubuntu20.04.5, Ubuntu22.04.1, Ubuntu22.10, Fedora36, RHEL8.6 etc.
  - All test passed.
 *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu22.04.1 and RHEL8.6.
  - All test passed.
* PF/VF(i40e, ixgbe): test scenarios including PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
        - Execution rate is 90%.
        - Known Bug "vf_interrupt_pmd/nic_interrupt_VF_vfio_pci: l3fwd-power Wake up failed" on X722 37d0. Intel Dev is still under investigating it.
* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.
        - Execution rate is 90%.
* idpf PMD and GVE PMD: basic test.
  - Under testing. Find one new bug about "[DPDK22.11] idpf: failed to start port all".
* 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 new issue is found.
* Power and IPsec:
 * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, etc.
        - Execution rate is 60%. No new issue is found yet.
 * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
        - Execution rate is 50%. No new issue is found yet.
# 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 yet.
* Cryptodev:
 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
        - Under testing.
 *Performance test: test scenarios including Throughput Performance /Cryptodev Latency, etc.
        - Under testing.

Best regards,
Yu Jiang

  parent reply	other threads:[~2022-11-17  8:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 17:32 Thomas Monjalon
2022-11-17  8:20 ` David Marchand
2022-11-17  8:48 ` Jiang, YuX [this message]
2022-11-21 13:50   ` Jiang, YuX
2022-11-21 14:13     ` Ferruh Yigit
2022-11-22 10:17     ` Jiang, YuX
2022-11-20 15:47 ` Wael Abualrub
2022-11-21 20:22 ` 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=BYAPR11MB27112F2A4F245E9349A9AAC6FE069@BYAPR11MB2711.namprd11.prod.outlook.com \
    --to=yux.jiang@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=michelle.devlin@intel.com \
    --cc=qi.z.zhang@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).