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>
Cc: "Devlin, Michelle" <michelle.devlin@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: RE: release candidate 22.11-rc2
Date: Thu, 10 Nov 2022 05:46:31 +0000	[thread overview]
Message-ID: <BYAPR11MB2711D53C9813772F5DC31D7FFE019@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BYAPR11MB271118481556BFB94184A863FE389@BYAPR11MB2711.namprd11.prod.outlook.com>

Hi All,

Update the test status for Intel part. Till now dpdk22.11-rc2 test is almost finished. No new critical issue is found.
Known Critical bug: [22.11-rc1]iavf macfwd performance drop 40%, Intel dev has reverted the patch, but no acked-by.
Meson test bugs:
  1, https://bugs.dpdk.org/show_bug.cgi?id=1118 [dpdk-22.11.0rc1][meson test] driver-tests/link_bonding_autotest test failed core dumped
    Can be fixed by https://patches.dpdk.org/project/dpdk/patch/20221031131744.2340150-1-ivan.malov@oktetlabs.ru/ & https://patches.dpdk.org/project/dpdk/patch/20221101161853.2702425-1-ivan.malov@oktetlabs.ru/
  2, 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.
  3, 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 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. Find 3 new issues. Intel Dev is under investigating it.
* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.
  - All test done. Find 2 new issue. Intel Dev is under investigating it.
  - Bug "[dpdk-22.11] ice_advanced_iavf_rss_gtpogre: create rule failed". 
    - Can be fixed by http://patches.dpdk.org/project/dpdk/patch/20221031064233.256917-1-stevex.yang@intel.com/	
* idpf PMD and GVE PMD: basic test.
  - All test done. Find 2 new issues.
  - Bug "Fail to configure port rxd/txd", can be fixed by https://patches.dpdk.org/project/dpdk/patch/20221109062913.18622-1-beilei.xing@intel.com/
  - Bug "tso can't take work", can be fixed by https://patches.dpdk.org/project/dpdk/patch/20221109011755.7964-1-beilei.xing@intel.com/
* 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, except Known Critical bug:[22.11-rc1]iavf macfwd performance drop 40%.
* Power and IPsec: 
 * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, etc. 
	- All test done. Find 1 new issue.
	- Bug "Uncore values unchanged and core dump when running uncore option with l3fwd-power", 
	  - can be fixed by https://patches.dpdk.org/project/dpdk/patch/20221104162353.187145-1-tadhg.kearney@intel.com/
 * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
	- All test done. Find 1 new issue.
	- Bug "IPSEC-SECGW Segfault when testing DPDK 22.11 RC2 validation", has fix.

# 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. 
    - Bug https://bugs.dpdk.org/show_bug.cgi?id=1119 [dpdk-22.11]pvp_virtio_bonding/vhost_virtio_bonding_mode_from_0_to_6: start bonding device failed and core dumped when quit testpmd"
      - Can be fixed by https://patches.dpdk.org/project/dpdk/patch/20221101161853.2702425-1-ivan.malov@oktetlabs.ru/
* Cryptodev: 
 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
	- All test done. Find two bugs.
	- Bug "[DPDK 22.11 RC2] Performance tests involving Software Crypto are failing", has fix and applied to dpdk-next-crypto.
	- Bug "[dpdk22.11 RC2] Unit test case is failing with segmentation fault", has fix and applied to dpdk-next-crypto.
 *Performance test: test scenarios including Throughput Performance /Cryptodev Latency, etc.
	- All test done. No big perf drop.

Best regards,
Yu Jiang

> -----Original Message-----
> From: Jiang, YuX
> Sent: Thursday, November 3, 2022 2:01 PM
> To: Thomas Monjalon <thomas@monjalon.net>; dev <dev@dpdk.org>
> Cc: Devlin, Michelle <michelle.devlin@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>
> Subject: RE: release candidate 22.11-rc2
> 
> Hi All,
> 
> Update the test status for Intel part. Till now dpdk22.11-rc2 test execution rate
> is 65%. No new critical issue is found, known critical issue is still under fixing.
> Known Critical bug: [22.11-rc1]iavf macfwd performance drop 40%, Intel dev
> has fix which is under verifying internally.
> Meson test bugs:
>   1, https://bugs.dpdk.org/show_bug.cgi?id=1118 [dpdk-22.11.0rc1][meson test]
> driver-tests/link_bonding_autotest test failed core dumped
>     Can be fixed by
> https://patches.dpdk.org/project/dpdk/patch/20221031131744.2340150-1-
> ivan.malov@oktetlabs.ru/ &
> https://patches.dpdk.org/project/dpdk/patch/20221101161853.2702425-1-
> ivan.malov@oktetlabs.ru/
>   2, 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.
> 
> # 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 80%. Find one new issue.
> 	- Bug "vf_interrupt_pmd/nic_interrupt_VF_vfio_pci: l3fwd-power Wake
> up failed" on X722 37d0. Intel Dev is 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 80%. Find one new issue.
> 	- Bug "[dpdk-22.11] ice_advanced_iavf_rss_gtpogre: create rule failed".
> 	  - Can be fixed by
> http://patches.dpdk.org/project/dpdk/patch/20221031064233.256917-1-
> stevex.yang@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 new issue is found, except Known Critical
> bug:[22.11-rc1]iavf macfwd performance drop 40%.
> * 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 30%. Find one issue, Intel dev is under investigating.
> # 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.
> 	- Bug https://bugs.dpdk.org/show_bug.cgi?id=1119 [dpdk-
> 22.11]pvp_virtio_bonding/vhost_virtio_bonding_mode_from_0_to_6: start
> bonding device failed and core dumped when quit testpmd"
> 	  - Can be fixed by
> https://patches.dpdk.org/project/dpdk/patch/20221101161853.2702425-1-
> ivan.malov@oktetlabs.ru/
> * Cryptodev:
>  *Function test: test scenarios including Cryptodev API testing/CompressDev
> ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
> 	- Under testing.
> 	- Bug "Performance tests involving Software Crypto are failing"
> 	  - Intel dev has provide patch:
> http://patchwork.dpdk.org/project/dpdk/patch/20221102232503.67970-1-
> kai.ji@intel.com/, which is under verifying.
>  *Performance test: test scenarios including Throughput Performance
> /Cryptodev Latency, etc.
> 	- Under testing.
> 
> Best regards,
> Yu Jiang
> 
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Tuesday, November 1, 2022 8:16 AM
> > To: announce@dpdk.org
> > Subject: release candidate 22.11-rc2
> >
> > A new DPDK release candidate is ready for testing:
> > 	https://git.dpdk.org/dpdk/tag/?id=v22.11-rc2
> >
> > There are 422 new patches in this snapshot.
> >
> > Release notes:
> > 	https://doc.dpdk.org/guides/rel_notes/release_22_11.html
> >
> > There were a lot of updates in drivers, including 3 new drivers:
> > 	- GVE (Google Virtual Ethernet)
> > 	- IDPF (Intel DataPlane Function or Infrastructure DataPath Function)
> > 	- UADK (User Space Accelerator Development Kit) supporting HiSilicon
> > crypto The driver features should be frozen now.
> >
> > Please test and report issues on bugs.dpdk.org.
> >
> > Thank you everyone
> >


  reply	other threads:[~2022-11-10  5:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  0:15 Thomas Monjalon
2022-11-03  6:01 ` Jiang, YuX
2022-11-10  5:46   ` Jiang, YuX [this message]
2022-11-10 16:14 ` 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=BYAPR11MB2711D53C9813772F5DC31D7FFE019@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=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).