patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: "Xu, HailinX" <hailinx.xu@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: 21.11.6 patches review and test
Date: Mon, 15 Jan 2024 10:25:47 +0000	[thread overview]
Message-ID: <87bc48c7-352c-40fb-b99e-e3ac4653c1f5@redhat.com> (raw)
In-Reply-To: <MW4PR11MB5912B911E5656AF19DB6DE9D9F6C2@MW4PR11MB5912.namprd11.prod.outlook.com>

On 15/01/2024 07:50, Xu, HailinX wrote:
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Wednesday, December 20, 2023 9:23 PM
>> To: stable@dpdk.org
>> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
>> Ali Alnubani <alialnu@nvidia.com>; benjamin.walker@intel.com; David
>> Christensen <drc@linux.vnet.ibm.com>; Hemant Agrawal
>> <hemant.agrawal@nxp.com>; Stokes, Ian <ian.stokes@intel.com>; Jerin Jacob
>> <jerinj@marvell.com>; Mcnamara, John <john.mcnamara@intel.com>; Ju-
>> Hyoung Lee <juhlee@microsoft.com>; Kevin Traynor
>> <ktraynor@redhat.com>; Luca Boccassi <bluca@debian.org>; Pei Zhang
>> <pezhang@redhat.com>; qian.q.xu@intel.com; Raslan Darawsheh
>> <rasland@nvidia.com>; Thomas Monjalon <thomas@monjalon.net>;
>> yanghliu@redhat.com; yuan.peng@intel.com; zhaoyan.chen@intel.com
>> Subject: 21.11.6 patches review and test
>>
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.6.
>>
>> The planned date for the final release is 12 January.
>>
>> Please help with testing and validation of your use cases and report any
>> issues/results with reply-all to this mail. For the final release the fixes and
>> reported validations will be added to the release notes.
>>
>> A release candidate tarball can be found at:
>>
>>     https://dpdk.org/browse/dpdk-stable/tag/?id=v21.11.6-rc1
>>
>> These patches are located at branch 21.11 of dpdk-stable repo:
>>     https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin
> 
> Update the test status for Intel part. completed dpdk21.11.6-rc1 all validation. No critical 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
>   Ubuntu20.04, Ubuntu22.04, Fedora35, Fedora38, RHEL8.9, RHEL9.2, FreeBSD13.2, SUSE15, CentOS7.9, 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.
> 

Thanks for testing and reporting! Kevin.

> 
> Regards,
> Xu, Hailin


      reply	other threads:[~2024-01-15 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 13:22 Kevin Traynor
2023-12-28  3:06 ` YangHang Liu
2024-01-09  9:43   ` Kevin Traynor
2024-01-03 14:43 ` Ali Alnubani
2024-01-09  9:41   ` Kevin Traynor
2024-01-09  9:48 ` Kevin Traynor
2024-01-10  1:28   ` Xu, HailinX
2024-01-10  9:46     ` Kevin Traynor
2024-01-15  7:50 ` Xu, HailinX
2024-01-15 10:25   ` Kevin Traynor [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=87bc48c7-352c-40fb-b99e-e3ac4653c1f5@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=hailinx.xu@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=stable@dpdk.org \
    /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).