From: "Xu, HailinX" <hailinx.xu@intel.com>
To: Xueming Li <xuemingl@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "xuemingl@nvdia.com" <xuemingl@nvdia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
Ali Alnubani <alialnu@nvidia.com>,
"Walker, Benjamin" <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>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
Yanghang Liu <yanghliu@redhat.com>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: RE: 22.11.3 patches review and test
Date: Tue, 29 Aug 2023 08:22:22 +0000 [thread overview]
Message-ID: <MW4PR11MB5912E951D2D904067C3938669FE7A@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230817061332.16248-1-xuemingl@nvidia.com>
> -----Original Message-----
> From: Xueming Li <xuemingl@nvidia.com>
> Sent: Thursday, August 17, 2023 2:14 PM
> To: stable@dpdk.org
> Cc: xuemingl@nvdia.com; dev@dpdk.org; Abhishek Marathe
> <Abhishek.Marathe@microsoft.com>; Ali Alnubani <alialnu@nvidia.com>;
> Walker, Benjamin <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>; Xu, Qian Q
> <qian.q.xu@intel.com>; Raslan Darawsheh <rasland@nvidia.com>; Thomas
> Monjalon <thomas@monjalon.net>; Yanghang Liu <yanghliu@redhat.com>;
> Peng, Yuan <yuan.peng@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Subject: 22.11.3 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 22.11.3.
>
> The planned date for the final release is 31th August.
>
> 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=v22.11.3-rc1
>
> These patches are located at branch 22.11 of dpdk-stable repo:
> https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
We are conducting DPDK testing and have found two issues.
1. The startup speed of testpmd is significantly slower in the os of SUSE
This issue fix patch has been merged into main, But it has not backported to 22.11.3.
Fix patch commit id on DPDK main: 7e7b6762eac292e78c77ad37ec0973c0c944b845
2. The SCTP tunnel packet of iavf cannot be forwarded in avx512 mode
commit 9b7215f150d0bfc5cb00fce68ff08e5217c7f2b3 on v22.11.3-rc1.
This commit is for the new feature (avx512 checksum offload) in DPDK 23.03, which should not be backported to the LTS version since avx512 checksum offload is not supported in v22.11.3 LTS.
Regards,
Xu, Hailin
next prev parent reply other threads:[~2023-08-29 8:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 6:13 Xueming Li
2023-08-24 16:02 ` Ali Alnubani
2023-08-25 6:41 ` Xueming(Steven) Li
2023-08-29 8:22 ` Xu, HailinX [this message]
2023-08-29 8:56 ` Xueming(Steven) Li
2023-08-31 1:50 ` Xu, HailinX
2023-08-31 6:36 ` Xueming(Steven) Li
2023-08-30 16:25 ` Kevin Traynor
2023-08-31 12:17 ` Kevin Traynor
2023-09-01 3:23 ` Zeng, ZhichaoX
2023-09-04 9:32 ` Kevin Traynor
2023-09-04 14:15 ` Kevin Traynor
2023-09-05 1:51 ` Zeng, ZhichaoX
2023-09-05 8:49 ` Kevin Traynor
2023-09-05 9:18 ` Xueming(Steven) Li
2023-09-05 5:37 ` Zeng, ZhichaoX
2023-08-29 16:03 ` YangHang Liu
2023-08-30 5:52 ` Xueming(Steven) Li
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=MW4PR11MB5912E951D2D904067C3938669FE7A@MW4PR11MB5912.namprd11.prod.outlook.com \
--to=hailinx.xu@intel.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=ktraynor@redhat.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvdia.com \
--cc=xuemingl@nvidia.com \
--cc=yanghliu@redhat.com \
--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).