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: [dpdk-dev] [dpdk-announce] release candidate 21.05-rc4
Date: Fri, 21 May 2021 09:47:18 +0000	[thread overview]
Message-ID: <SJ0PR11MB515048919661ED4729251686FE299@SJ0PR11MB5150.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1994252.qWktbAlWXN@thomas>

All,

Update the test status for Intel part. Till now dpdk21.05-rc4 test is almost finished and no new issue is found.

# 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, CentOS Stream 8, etc.
                        - All passed.
                        - Bug about "crypto_zuc build failed on Fedora34 with gcc 11" has been fixed in RC4.
                *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20.04 and CentOS Stream 8.
                        - All passed.

        * PF(i40e, ixgbe and igb): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
                - All tests are done, no new issue is found except known issue.
                - 1 bug is reported based on rc1 in bugzilla. Patch has provided but need other patch supports, all of them will be fixed in next release.
                        > * https://bugs.dpdk.org/show_bug.cgi?id=687

        * VF(i40e, ixgbe and igb): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
                - All tests are done. No new issue is found except known issue.

        * PF/VF(ICE): test scenarios including /Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Share code update/Flexible Descriptor, etc.
                - All tests are done. No new issue is found except known issues.

        * Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc.
                - Test important part. No new issue is found.

        * Power and IPsec:
                * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency and so on.
                        - All passed. No new issue is found.
                * IPsec: test scenarios including ipsec/ipsec-secgw
                        - Not tested in RC4. Tested in RC1~RC3, no issue is found.

# 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.0u2, etc.
                - All tests are done.
                - No new issue is found except known issues which are found in rc2.
                - Bug https://bugs.dpdk.org/show_bug.cgi?id=699  has been fixed in RC4.

        * Cryptodev:
                *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
                        - All tests are done. No new bug is found except known issue.
                *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
                        - All tests are done.

Best regards,
Yu Jiang

>-----Original Message-----
>From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
>Sent: Thursday, May 20, 2021 5:47 AM
>To: announce@dpdk.org
>Subject: [dpdk-dev] [dpdk-announce] release candidate 21.05-rc4
>
>A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v21.05-rc4
>
>There are only 48 new patches in this snapshot, meaning this release cycle is
>almost closed.
>
>Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_21_05.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.
>
>If no issue, DPDK 21.05 should be released at the end of this week.
>
>Please think about sharing your roadmap for DPDK 21.08.
>
>Thank you everyone
>


      reply	other threads:[~2021-05-21  9:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 21:46 Thomas Monjalon
2021-05-21  9:47 ` Jiang, YuX [this message]

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=SJ0PR11MB515048919661ED4729251686FE299@SJ0PR11MB5150.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).