From: Luca Boccassi <bluca@debian.org>
To: "Jiang, YuX" <yux.jiang@intel.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Walker, Benjamin" <benjamin.walker@intel.com>
Subject: Re: 21.11.2 patches review and test
Date: Tue, 16 Aug 2022 12:39:48 +0100 [thread overview]
Message-ID: <53fd041c07885a3f9eb79dc752e63ecd9f99513e.camel@debian.org> (raw)
In-Reply-To: <BYAPR11MB2711DA581B5ACBC7C4174004FE9F9@BYAPR11MB2711.namprd11.prod.outlook.com>
On Thu, 2022-08-04 at 07:28 +0000, Jiang, YuX wrote:
> > -----Original Message-----
> > From: Jiang, YuX <yux.jiang@intel.com>
> > Sent: Tuesday, August 2, 2022 6:15 PM
> > To: Luca Boccassi <bluca@debian.org>; stable@dpdk.org
> > Cc: dev@dpdk.org; Walker, Benjamin <benjamin.walker@intel.com>;
> > Raslan
> > Darawsheh <rasland@nvidia.com>; Thomas Monjalon
> > <thomas@monjalon.net>; yanghliu@redhat.com
> > Subject: RE: 21.11.2 patches review and test
> >
> > > -----Original Message-----
> > > From: Luca Boccassi <bluca@debian.org>
> > > Sent: Tuesday, August 2, 2022 6:01 PM
> > > To: Jiang, YuX <yux.jiang@intel.com>; stable@dpdk.org
> > > Cc: dev@dpdk.org; Walker, Benjamin <benjamin.walker@intel.com>;
> > Raslan
> > > Darawsheh <rasland@nvidia.com>; Thomas Monjalon
> > <thomas@monjalon.net>;
> > > yanghliu@redhat.com
> > > Subject: Re: 21.11.2 patches review and test
> > >
> > > On Fri, 2022-07-29 at 11:26 +0000, Jiang, YuX wrote:
> > > > > -----Original Message-----
> > > > > From: Jiang, YuX
> > > > > Sent: Friday, July 29, 2022 11:01 AM
> > > > > To: Luca Boccassi <bluca@debian.org>; stable@dpdk.org
> > > > > Cc: 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>; Pei Zhang <pezhang@redhat.com>; Xu,
> > > > > Qian
> > Q
> > > > > <qian.q.xu@intel.com>; Raslan Darawsheh <rasland@nvidia.com>;
> > > Thomas
> > > > > Monjalon <thomas@monjalon.net>; Peng, Yuan
> > > <yuan.peng@intel.com>;
> > > > > Chen, Zhaoyan <zhaoyan.chen@intel.com>; yanghliu@redhat.com
> > > > > Subject: RE: 21.11.2 patches review and test
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Luca Boccassi <bluca@debian.org>
> > > > > > Sent: Thursday, July 28, 2022 8:34 PM
> > > > > > To: stable@dpdk.org
> > > > > > Cc: 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>; Pei
> > > > > Zhang
> > > > > > <pezhang@redhat.com>; Xu, Qian Q <qian.q.xu@intel.com>;
> > > > > > Raslan
> > > > > > Darawsheh <rasland@nvidia.com>; Thomas Monjalon
> > > > > <thomas@monjalon.net>;
> > > > > > Peng, Yuan <yuan.peng@intel.com>; Chen, Zhaoyan
> > > > > > <zhaoyan.chen@intel.com>; yanghliu@redhat.com
> > > > > > Subject: Re: 21.11.2 patches review and test
> > > > > >
> > > > > > On Mon, 2022-07-18 at 10:58 +0100, luca.boccassi@gmail.com
> > > > > > wrote:
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Here is a list of patches targeted for stable release
> > > > > > > 21.11.2.
> > > > > > >
> > > > > > > The planned date for the final release is August 29th.
> > > > > > >
> > > > > > > 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.2-rc1
> > > > > > >
> > > > > > > These patches are located at branch 21.11 of dpdk-stable
> > > > > > > repo:
> > > > > > > https://dpdk.org/browse/dpdk-stable/
> > > > > > >
> > > > > > > Thanks.
> > > > > > >
> > > > > > > Luca Boccassi
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > Any update from any of the validation teams? Any indication
> > > > > > on
> > > > > > how the tests are going?
> > > > > >
> > > > > > --
> > > > > > Kind regards,
> > > > > > Luca Boccassi
> > > > >
> > > > > Everything is fine, find one vhost related issue which is
> > > > > investigated by Intel Dev.
> > > > > I will send a v1 report later. Thanks.
> > > > >
> > > > > Best regards,
> > > > > Yu Jiang
> > > >
> > > > Update the test status for Intel part. Till now dpdk21.11.2-rc1
> > > > test
> > > > rate is 90%, no critical issue is found.
> > > > Failure defects as below:
> > > > Bug1: [dpdk v21.11.2-rc1] examples/performance-thread meson
> > > > build error with gcc12.1 on fedora36
> > > > Bug2: DPDK 21.11.1 cryptodev_qat_raw_api_autotest failing
> > > > - Intel Dev send a patch to skip oop test for raw api,
> > > > need
> > > > be reviewed and merged.
> > >
> > > Hi,
> > >
> > > Do you have a reference to this patch? I did not see anything new
> > > sent
> > > to stable in the past week or so
> > >
> >
> > Yes, he only send an attached file, I will check this with Intel
> > Dev. Thanks.
> >
> > > > Bug3: [21.11LTS]Test with the new local patch, Vhost-user
> > > > meet
> > > > Segmentation fault issue when quit virtio-user before stopping
> > > > sending packets
> > > > - Intel Dev is under investigating.
> > --- Intel Dev is preparing dpdk patch~, Thanks.
> >
> > Best regards,
> > Yu Jiang
> > > >
> Update the test status for Intel part. dpdk21.11.2-rc1 validation
> test is finished, no critical issue is found.
> No new bug except the above three bugs.
> Update bug's status as below:
> Bug1: [dpdk v21.11.2-rc1] examples/performance-thread meson build
> error with gcc12.1 on fedora36
> - https://bugs.dpdk.org/show_bug.cgi?id=1061
> - No fix yet.
> Bug2: DPDK 21.11.1 cryptodev_qat_raw_api_autotest failing
> - Intel Dev send a patch file to skip oop test for raw api,
> but not send it to stable@dpdk.org, we will check this with Intel
> Dev.
Hi,
Any update on the above 2 issues?
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2022-08-16 11:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 9:58 luca.boccassi
2022-07-19 2:40 ` Pei Zhang
2022-07-28 12:34 ` Luca Boccassi
2022-07-28 12:48 ` Ali Alnubani
2022-08-16 7:33 ` Ali Alnubani
2022-08-16 10:05 ` Luca Boccassi
2022-07-29 3:00 ` Jiang, YuX
2022-07-29 11:26 ` Jiang, YuX
2022-08-02 10:00 ` Luca Boccassi
2022-08-02 10:14 ` Jiang, YuX
2022-08-04 7:28 ` Jiang, YuX
2022-08-16 11:39 ` Luca Boccassi [this message]
2022-08-17 10:00 ` Jiang, YuX
2022-08-26 8:13 ` Jiang, YuX
2022-08-26 9:06 ` Kevin Traynor
2022-08-02 3:29 ` YangHang Liu
2022-08-02 9:32 ` Luca Boccassi
2022-08-29 13:00 ` Stokes, Ian
2022-08-29 16:20 ` Kevin Traynor
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=53fd041c07885a3f9eb79dc752e63ecd9f99513e.camel@debian.org \
--to=bluca@debian.org \
--cc=benjamin.walker@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=yux.jiang@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).