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: Mon, 21 Nov 2022 13:50:45 +0000	[thread overview]
Message-ID: <BYAPR11MB27114256FBD2E3B285DCEC12FE0A9@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BYAPR11MB27112F2A4F245E9349A9AAC6FE069@BYAPR11MB2711.namprd11.prod.outlook.com>

> -----Original Message-----
> From: Jiang, YuX
> Sent: Thursday, November 17, 2022 4:49 PM
> 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
>
> > -----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 validation test is almost finished.
3 bugs are found, Bug1 & Bug2 are critical issues, hope they can be fixed in 22.11.
  Bug1: https://bugs.dpdk.org/show_bug.cgi?id=1128 [dpdk22.11-rc3]failed to start testpmd with the mbuf-size parameter
    - Bad commit 4f04edcda769770881832f8036fd209e7bb6ab9a
    - Verify v4 dpdk patch(https://patches.dpdk.org/project/dpdk/patch/20221118141334.3825072-1-hpothula@marvell.com/), test passed.
  Bug2: idpf: core dumped when launch l3fwd with 1c1q. Verify patches passed, hope it can be merged into RC4.
    - patch link: https://patches.dpdk.org/project/dpdk/patch/20221118070246.114513-1-beilei.xing@intel.com/ & https://patches.dpdk.org/project/dpdk/patch/20221118035039.106084-1-beilei.xing@intel.com/
  Bug3: [DPDK22.11] idpf: failed to start port all. Verify patch 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.
        - All test done. No new issue is found.
        - Known Bug "vf_interrupt_pmd/nic_interrupt_VF_vfio_pci: l3fwd-power Wake up failed" on X722 37d0. Verify patch passed.
                - patch link: https://patchwork.dpdk.org/project/dpdk/patch/20221117065726.277672-1-kaisenx.you@intel.com/
* 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 issue is found.
* idpf PMD and GVE PMD: basic test.
        - All test done. Find Bug2 & Bug3 on idpf PMD.
* 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 and other modules:
 * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, etc.
        - All test done. No new issue is found.
 * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
        - All test done. No new issue is found.
# 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 done. No new issue is found.
 *Performance test: test scenarios including Throughput Performance /Cryptodev Latency, etc.
        - All test done. No big performance drop.

Best regards,
Yu Jiang

  reply	other threads:[~2022-11-21 13:50 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
2022-11-21 13:50   ` Jiang, YuX [this message]
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=BYAPR11MB27114256FBD2E3B285DCEC12FE0A9@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).