From: Luca Boccassi <bluca@debian.org>
To: "Xu, HailinX" <hailinx.xu@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>,
"benjamin.walker@intel.com" <benjamin.walker@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
"yuan.peng@intel.com" <yuan.peng@intel.com>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: Re: 22.11.6 patches review and test
Date: Fri, 9 Aug 2024 11:26:29 +0100 [thread overview]
Message-ID: <CAMw=ZnRh=9-XN9piM0Nq2eLNAyuxSME=gF-os6pisTrZ93-LZw@mail.gmail.com> (raw)
In-Reply-To: <MW4PR11MB5912A30E38E96E68A75BDEDE9FBA2@MW4PR11MB5912.namprd11.prod.outlook.com>
On Fri, 9 Aug 2024 at 11:20, Xu, HailinX <hailinx.xu@intel.com> wrote:
>
> Update the test status for Intel part. dpdk22.11.6-rc1 all validation test done. no new issue is found.
>
> # Basic Intel(R) NIC testing
> * Build & CFLAG compile: cover the build test combination with latest GCC/Clang version and the popular OS revision such as
> Ubuntu24.04, Ubuntu22.04, Fedora40, RHEL9.3, RHEL9.4, FreeBSD14.0, SUSE15, CentOS7.9, openEuler22.03-SP1,OpenAnolis8.8 etc.
> - All test done. No new dpdk issue is found.
> * PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> - All test done. No new dpdk issue is found.
> * VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> - All test done. No new dpdk issue is found.
> * PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.
> - All test done. No new dpdk issue is found.
> * Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, etc.
> - All test done. No new dpdk issue is found.
> * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
> - All test done. No new dpdk 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 8.0, etc.
> - All test done. No new dpdk issue is found.
> * Cryptodev:
> *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
> - All test done. No new dpdk issue is found.
> *Performance test: test scenarios including Thoughput Performance/Cryptodev Latency, etc.
> - All test done. No new dpdk issue is found.
Thank you!
next prev parent reply other threads:[~2024-08-09 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 19:37 luca.boccassi
2024-08-01 11:59 ` Luca Boccassi
2024-08-05 5:45 ` YangHang Liu
2024-08-05 12:27 ` Luca Boccassi
2024-08-09 10:19 ` Xu, HailinX
2024-08-09 10:26 ` Luca Boccassi [this message]
2024-08-15 11:10 ` Luca Boccassi
2024-08-15 16:19 ` Ali Alnubani
2024-08-15 16:21 ` Luca Boccassi
2024-08-20 7:21 ` Ali Alnubani
2024-08-20 8:58 ` Luca Boccassi
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='CAMw=ZnRh=9-XN9piM0Nq2eLNAyuxSME=gF-os6pisTrZ93-LZw@mail.gmail.com' \
--to=bluca@debian.org \
--cc=benjamin.walker@intel.com \
--cc=dev@dpdk.org \
--cc=hailinx.xu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qian.q.xu@intel.com \
--cc=stable@dpdk.org \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).