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-rc2
Date: Tue, 11 May 2021 11:18:47 +0000	[thread overview]
Message-ID: <SJ0PR11MB5150E9B661923E5695B012A4FE539@SJ0PR11MB5150.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3585896.ctXz43JjJv@thomas>

All,

Update the test status for Intel part. Till now dpdk21.05-rc2 test is almost finished, find 1 critical bad commit id: "b7aaf417f9 raw/ioat: add bus driver for device scanning automatically",
which blocked most of VF/kni test. Bruce has worked on this and has provided patch(http://patches.dpdk.org/project/dpdk/patch/20210506150908.797110-1-bruce.richardson@intel.com/ ) to fix.
The patch has been verified passed by Validation team and applied by Thomas in May-10.

# 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.
                *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.
                - 3 new bugs about critical bad commit id and DPDK PF+DPDK VF:launch testpmd failed by using VF are found.
                - 7 bugs are found in RC1 still not be fixed. 2 bugs have dpdk patch which is not merged, 2 bugs are belong to HSD issue.
                        > 3 bugs are reported in bugzilla:
                                * https://bugs.dpdk.org/show_bug.cgi?id=687
                                * https://bugs.dpdk.org/show_bug.cgi?id=688   (nvidia dev has provided patch, but not be merged in RC2.)
                                * https://bugs.dpdk.org/show_bug.cgi?id=693
                        > Other bugs are about csum fwd mode can not transmit packet,i40e ddp_gtp flow_director_filter take no effect, etc. Intel Dev. are working on them.

        * VF(i40e, ixgbe and igb): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
                - All tests are done. Besides issue about DPDK PF+DPDK VF: launch testpmd failed by using VF blocked test, others are known issues.

        * 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.
                - 2 bugs about rss_pppoe add rss cfg failed and ip_fragment_pf_rss hash issue are found in RC2, others are known issues.
                - Issues about QinQ&DCF issues in RC1 have been fixed in RC2, GTPOGRE issue has dpdk patch, but not been merged in RC2. Intel Dev. are working on other bugs.

        * Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc.
                - All passed.
                - Issue about perf drops about 20% when use iavf to test multi-queue single core performance in RC1 has been fixed in RC2.

        * Power and IPsec:
                * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency and so on.
                        - All tests are done. Besides critical bad commit id issue, no new issue is found.
                        - Issue about launch dpdk-l3fwd-power failed in RC1 has been fixed in RC2.
                * IPsec: test scenarios including ipsec/ipsec-secgw
                        - All tests are failed due to critical bad commit id b7aaf417f9, but test passed by using Bruce's new patch.
                        - Issue about ipsec-secgw test failed is found in RC1 has been fixed in RC2.

# 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.
                - 3 new issues are found except known issue.
                        > 1 bug is reported in bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=699

        * Cryptodev:
                *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
                        - All passed except known issue.
                *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
                        - All passed. No big perf drop.

Best regards,
Yu Jiang

>-----Original Message-----
>From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
>Sent: Thursday, May 6, 2021 7:04 AM
>To: announce@dpdk.org
>Subject: [dpdk-dev] [dpdk-announce] release candidate 21.05-rc2
>
>A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v21.05-rc2
>
>There are 296 new patches in this snapshot, most of them adding or fixing
>features in drivers.
>
>Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_21_05.html
>
>Please test and report issues on bugs.dpdk.org.
>
>DPDK 21.05-rc3 is expected in one week.
>If there are exceptional issues to meet the schedule, especially in India, let's
>discuss how we can accomodate.
>
>Thank you everyone, take care.
>


  reply	other threads:[~2021-05-11 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-05 23:03 Thomas Monjalon
2021-05-11 11:18 ` Jiang, YuX [this message]
2021-05-11 23:28 ` 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=SJ0PR11MB5150E9B661923E5695B012A4FE539@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).