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>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "Devlin, Michelle" <michelle.devlin@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: RE: release candidate 22.03-rc3
Date: Thu, 10 Mar 2022 08:57:34 +0000	[thread overview]
Message-ID: <BYAPR11MB2711662E1139B243DFD3CFBCFE0B9@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3941088.BzM5BlMlMQ@thomas>

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, March 9, 2022 7:44 AM
> To: announce@dpdk.org
> Subject: release candidate 22.03-rc3
>
> A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v22.03-rc3
>
> There are 102 new patches in this snapshot.
>
> Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_22_03.html
>
> This should be the last release candidate.
> Only documentation and critical bug fixes are accepted until the release.
>
> 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.
>
> Please think about sharing your roadmap now for DPDK 22.07.
>
> Thank you everyone
>

Update the test status for Intel part. Till now dpdk22.03-rc3 test execution rate is 60%. No critical issue is found.

There are three bugs which have fix but not been merged into rc3, please review and merge if possible.
Bug1, Known issue: https://bugs.dpdk.org/show_bug.cgi?id=939
  >It has fix but not merged into rc3, patch is delegate to "Jerin Jacob".  Please review and merge if possible.
  > http://patchwork.dpdk.org/project/dpdk/patch/20220304142337.911828-1-rkudurumalla@marvell.com/
Bug2, Known issue about "dpdk_gso_lib/test_vhost_gso_with_vxlan: VM can't send ICMP packet to host namespace".
 > it has fix but not merged into rc3, patch is delegate to "Ferruh Yigit". Please review and merge if possible.
 > http://patchwork.dpdk.org/project/dpdk/patch/20211229093702.1930214-3-kevinx.liu@intel.com/
Bug3, Known issue about "GRO/GSO feature test need to modify dpdk code"
 > It has fix but not merged into rc3, patch is delegated to "Maxime Coquelin". Please review and merge if possible.
 > https://patches.dpdk.org/project/dpdk/patch/20220217151628.441165-1-wenwux.ma@intel.com/

# Basic Intel(R) NIC testing
* Build or compile:
 *Build: cover the build test combination with latest GCC/Clang/ICC version and the popular OS revision such as Ubuntu20.04, Fedora35, RHEL8.4, RHEL8.5 etc.
  - All test passed.
  - One known issue https://bugs.dpdk.org/show_bug.cgi?id=928, use "meson setup -Ddisable_drivers=event/cnxk" to build.
 *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20.04 and RHEL8.4.
  - All test done. One known issue is Bug1.

* PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
 - Execution rate is 40%. No new issue is found.

* VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
 - Execution rate is 40%. 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.
 - Execution rate is 80%. 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.
 - Execution rate is 50%. No big performance drop.

# 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. Two known bugs: Bug2 and Bug3.

* Cryptodev:
 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
  - Execution rate is 20%. Two known issues, Intel dev is investigating.
 *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
  - Execution rate is 20%.

  reply	other threads:[~2022-03-10  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 23:43 Thomas Monjalon
2022-03-10  8:57 ` Jiang, YuX [this message]
2022-03-14 11:46   ` Jiang, YuX
2022-03-10 13:33 ` Wael Abualrub
2022-03-12 23:48 ` 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=BYAPR11MB2711662E1139B243DFD3CFBCFE0B9@BYAPR11MB2711.namprd11.prod.outlook.com \
    --to=yux.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=maxime.coquelin@redhat.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).