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>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: RE: release candidate 22.03-rc1
Date: Thu, 17 Feb 2022 05:30:45 +0000	[thread overview]
Message-ID: <BYAPR11MB27112B50E6BBBBA1F3B0FA68FE369@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3863085.e99z0qppnp@thomas>

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Monday, February 14, 2022 8:58 AM
> To: announce@dpdk.org
> Subject: release candidate 22.03-rc1
>
> A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v22.03-rc1
>
> There are 481 new patches in this snapshot.
> This release cycle is quiet and should be small.
>
> Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_22_03.html
>
> Highlights of 22.03-rc1:
>       - fast restart by reusing hugepages
>       - UDP/TCP checksum on multi-segments
>       - IP reassembly offload
>       - queue-based priority flow control
>       - private ethdev driver info dump
>       - private user data in asymmetric crypto session
>
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 22.03-rc2 is expected in two weeks.
>
> Thank you everyone
>
# 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.
  - Two known issue, one ishttps://bugs.dpdk.org/show_bug.cgi?id=928 still exist;
  other is about dpdk-next-virtio/dpdk-next-net-brcm I40E/ICE_16BYTE_RX_DESC meson build failure with gcc10.3 on ubuntu20.04,due to miss patch:
  http://patches.dpdk.org/project/dpdk/patch/20220208154219.266278-1-yidingx.zhou@intel.com/, please backport this patch to the two next branch.
*Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20.04 and RHEL8.4.
 - All test passed.
* PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
 - Execution rate is 80%. No new issue is found yet.
* VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
 - Execution rate is 80%.
 - Known issue about "vf tso: the larger tcp pkt not segmented correct fragments" has v2 fix:
 https://patches.dpdk.org/project/dpdk/patch/20220215155023.1542072-1-radu.nicolau@intel.com/
* 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%. Four new bugs are found, Intel devs are under investigating.
* 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 big performance drop.
* Power and IPsec:
 * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, etc.
  - Execution rate is 90%, no new issue is found.
 * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
  - All test passed.
# 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 new bugs are found, Intel devs are under investigating.
* Cryptodev:
 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
  - Execution rate is 60%, no new issue is found.
 *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
  - Execution rate is 60%. No big performance drop.

  reply	other threads:[~2022-02-17  5:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14  0:58 Thomas Monjalon
2022-02-17  5:30 ` Jiang, YuX [this message]
2022-02-24  2:30   ` Jiang, YuX

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