DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, HailinX" <hailinx.xu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Kovacevic, Marko" <marko.kovacevic@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: RE: release candidate 23.03-rc3
Date: Mon, 27 Mar 2023 01:51:01 +0000	[thread overview]
Message-ID: <MW4PR11MB591282E4DCDE1CC5425041CC9F8B9@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW4PR11MB59129F04FEEE530D1BFF40BD9F879@MW4PR11MB5912.namprd11.prod.outlook.com>

> -----Original Message-----
> From: Xu, HailinX
> Sent: Thursday, March 23, 2023 4:23 PM
> To: Thomas Monjalon <thomas@monjalon.net>; dev@dpdk.org
> Cc: Kovacevic, Marko <Marko.Kovacevic@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>;
> Ferruh Yigit <ferruh.yigit@xilinx.com>
> Subject: RE: release candidate 23.03-rc3
> 
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Tuesday, March 21, 2023 12:30 AM
> > To: announce@dpdk.org
> > Subject: release candidate 23.03-rc3
> >
> > A new DPDK release candidate is ready for testing:
> > 	https://git.dpdk.org/dpdk/tag/?id=v23.03-rc3
> >
> > There are 110 new patches in this snapshot.
> >
> > Release notes:
> > 	https://doc.dpdk.org/guides/rel_notes/release_23_03.html
> >
> > Few major additions arrived in this -rc3:
> > 	- test application for machine learning inference
> > 	- DTS hello world
> > The test framework DTS is being improved and migrated into the mainline.
> > Please join the DTS effort for contributing, reviewing or testing.
> >
> > As usual, you can report any issue on https://bugs.dpdk.org
> >
> > DPDK 23.03-rc4 could be out at the end of this week.
> >
> > Thank you everyone
> >
> Update the test status for Intel part. Till now dpdk23.03-rc3 test execution rate is
> 85%, no new issue is found.
> # 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, Fedora37,
> RHEL8.6/9.1 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.
> * Meson test & Asan test:
>   known issues:
>         - https://bugs.dpdk.org/show_bug.cgi?id=956 [dpdk-22.03][asan]
> dpdk-pdump: detected memory leaks when quit dpdk-pdump
>                 - Not fix yet.
>         - https://bugs.dpdk.org/show_bug.cgi?id=1024 [dpdk-22.07][meson
> test] driver-tests/link_bonding_mode4_autotest bond handshake failed
>                 - Not fix yet.
>         - https://bugs.dpdk.org/show_bug.cgi?id=1107 [22.11-rc1][meson test]
> seqlock_autotest test failed.
>                 - Special issue with gcc 4.8.5.
> * 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.
> * 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.
> * 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 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.
>  * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test -
> QAT&SW/FIB library, etc.
>         - On going.
> # 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 8.0, 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.
>         - On going.
>  *Performance test: test scenarios including Throughput Performance
> /Cryptodev Latency, etc.
>         - On going.
> 
> Regards,
> Xu, Hailin
Update the test status for Intel part. Till now dpdk23.03-rc3 all test done, no new issue is found.
# 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, Fedora37, RHEL8.6/9.1 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.
* Meson test & Asan test:
  known issues:
        - https://bugs.dpdk.org/show_bug.cgi?id=956 [dpdk-22.03][asan] dpdk-pdump: detected memory leaks when quit dpdk-pdump
                - Not fix yet.
        - https://bugs.dpdk.org/show_bug.cgi?id=1024 [dpdk-22.07][meson test] driver-tests/link_bonding_mode4_autotest bond handshake failed
                - Not fix yet.
        - https://bugs.dpdk.org/show_bug.cgi?id=1107 [22.11-rc1][meson test] seqlock_autotest test failed.
                - Special issue with gcc 4.8.5.
* 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.
* 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.
* 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 new issue is found.
* Power and IPsec:
 * 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 8.0, 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 new issue is found.

Regards,
Xu, Hailin

  reply	other threads:[~2023-03-27  1:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 16:29 Thomas Monjalon
2023-03-23  8:23 ` Xu, HailinX
2023-03-27  1:51   ` Xu, HailinX [this message]
2023-03-26 12:07 ` Wael Abualrub
2023-03-28  8:14 ` David Marchand

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=MW4PR11MB591282E4DCDE1CC5425041CC9F8B9@MW4PR11MB5912.namprd11.prod.outlook.com \
    --to=hailinx.xu@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@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).