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>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: RE: release candidate 22.07-rc2
Date: Thu, 30 Jun 2022 08:31:33 +0000	[thread overview]
Message-ID: <BYAPR11MB2711578DF90FC3B2BB580687FEBA9@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4109670.NACDBdzCOe@thomas>

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Monday, June 27, 2022 10:15 AM
> To: announce@dpdk.org
> Subject: release candidate 22.07-rc2
>
> A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v22.07-rc2
>
> There are 317 new patches in this snapshot.
>
> Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_22_07.html
>
> There were a lot of updates in drivers.
> The driver features should be frozen now.
>
> Please test and report issues on bugs.dpdk.org.
> Do not forget to review examples and documentation updates.
>
> DPDK 22.07-rc3 is expected in one week (targetting end of June).
>
> Thank you everyone
>

Update the test status for Intel part. Till now dpdk22.07-rc2 test execution rate is 85%. Till now, two P2-high issues are found.
Intel Dev have provided fix and test passed, other common issues need to be confirmed and fixed by Intel Dev.

# 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 85%. Find 3 new issues, two have fix, other is under investigating.

* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.
        - Execution rate is 100%.
        - Find 1 new issue about "ice_iavf_fdir: the ipv4/6 gtpu_eh rule not take effect",
                - bad commit id is commit 0718b7716c9516fca458695f7a0195b1f45d4778 (HEAD, refs/bisect/bad)
                        Author: Gregory Etelson <getelson@nvidia.com>
                        Date:   Thu Jun 16 21:01:03 2022 +0300
                        net: fix GTP PSC headers

* 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 100%, all passed.  No big performance drop.

* Power and IPsec:
 * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, etc.
  - All test passed.
 * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
        - Execution rate is 20%. Known issue: https://bugs.dpdk.org/show_bug.cgi?id=1034, V2 patch is under verified.

# 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.
        - Execution rate is 90%. Find 2 new issue. Intel dev is under investigating.

* Cryptodev:
 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
        - Execution rate is 90%. Find 1 new issues. Intel dev is under investigating.
 *Performance test: test scenarios including Throughput Performance /Cryptodev Latency, etc.
        - Execution rate is 90%.  No new issue is found.

Best regards,
Yu Jiang

  reply	other threads:[~2022-06-30  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  2:15 Thomas Monjalon
2022-06-30  8:31 ` Jiang, YuX [this message]
2022-07-04  9:58   ` Jiang, YuX
2022-07-01 14:27 ` Ferruh Yigit
2022-07-02  1:33 ` 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=BYAPR11MB2711578DF90FC3B2BB580687FEBA9@BYAPR11MB2711.namprd11.prod.outlook.com \
    --to=yux.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=michelle.devlin@intel.com \
    --cc=qi.z.zhang@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).