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>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: RE: release candidate 22.07-rc3
Date: Thu, 7 Jul 2022 09:07:28 +0000	[thread overview]
Message-ID: <BYAPR11MB2711F13CDA2B0A4535A6591EFE839@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3238436.3CdzvNlvnA@thomas>

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, July 6, 2022 4:36 AM
> To: announce@dpdk.org
> Subject: release candidate 22.07-rc3
>
> A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v22.07-rc3
>
> There are 82 new patches in this snapshot.
>
> Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_22_07.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.
>
> DPDK 22.07-rc4 should be the last chance for bug fixes and doc updates.
> Do not forget to review pending patches for examples and documentation.
>
> Please think about sharing your roadmap now for DPDK 22.11.
>
> Thank you everyone
>

Update the test status for Intel part. Till now dpdk22.07-rc3 test execution rate is 65%, find 2 new bugs, No.2 is critical bug.
No.1, "Bug 1048 - [dpdk-22.07rc3] i40e_rss_input/flow_query: RSS types is not displayed tests failed". Only display failed, there is no fix yet.
No.2, [dpdk-22.07rc3]The performance of X710 drop about 45% when testing nic_single_core: has fix and verify passed.
http://patchwork.dpdk.org/project/dpdk/patch/20220707162602.2123584-1-kevinx.liu@intel.com/  ---Need push to merge.

Known critical bugs:
1, The performance of virtio PVP multi_paths has a drop(~about 5%) between DPDK22.07-rc2 and DPDK-22.03
split ring has fix, http://patchwork.dpdk.org/project/dpdk/patch/20220707065513.66458-1-xuan.ding@intel.com/  ---Need verify then need push to merge.
packed ring has no fix, Intel Dev is investigating.
2, Bug 1044 - [dpdk-22.07] ice_iavf_fdir: the ipv4/6 gtpu_eh rule not take effect
has fix, http://patches.dpdk.org/project/dpdk/patch/20220706025626.1070737-1-wenxuanx.wu@intel.com/   ---Need push to merge.

# 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, Ubuntu22.04, Fedora36, RHEL8.6 etc.
  - 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 1 new bug: "Bug 1048 - [dpdk-22.07rc3] i40e_rss_input/flow_query: RSS types is not displayed tests failed". There is no fix yet.

* 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%. No new bug is found.

* 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%. Find 1 critical bug:[dpdk-22.07rc3]The performance of X710 drop about 45% when testing nic_single_core: has fix and verify passed.

# Basic 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%. No new bug is found.

Best regards,
Yu Jiang

  reply	other threads:[~2022-07-07  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 20:35 Thomas Monjalon
2022-07-07  9:07 ` Jiang, YuX [this message]
2022-07-11  9:35   ` Jiang, YuX
2022-07-07 13:38 ` Wael Abualrub

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=BYAPR11MB2711F13CDA2B0A4535A6591EFE839@BYAPR11MB2711.namprd11.prod.outlook.com \
    --to=yux.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.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).