From: Luca Boccassi <bluca@debian.org>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dpdk stable <stable@dpdk.org>, dev <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Ali Alnubani <alialnu@nvidia.com>,
benjamin.walker@intel.com,
David Christensen <drc@linux.vnet.ibm.com>,
hariprasad.govindharajan@intel.com,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Ian Stokes <ian.stokes@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Kevin Traynor <ktraynor@redhat.com>,
Pei Zhang <pezhang@redhat.com>,
pingx.yu@intel.com, qian.q.xu@intel.com,
Raslan Darawsheh <rasland@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
yuan.peng@intel.com, zhaoyan.chen@intel.com
Subject: Re: [dpdk-stable] [dpdk-dev] 20.11.1 patches review and test
Date: Thu, 25 Feb 2021 10:14:04 +0000 [thread overview]
Message-ID: <943c21dac28bb70c4d5448066010aca820cc70f6.camel@debian.org> (raw)
In-Reply-To: <CAATJJ0LsUbOkrpYWcE5UMR7gwbWMFYfAjv=uk+S69tDhL6OKyQ@mail.gmail.com>
On Thu, 2021-02-25 at 10:43 +0100, Christian Ehrhardt wrote:
> On Mon, Feb 22, 2021 at 4:09 PM <luca.boccassi@gmail.com> wrote:
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 20.11.1.
> >
> > The planned date for the final release is the 8th of March.
> >
> > 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=v20.11.1-rc1
> >
> > These patches are located at branch 20.11 of dpdk-stable repo:
> > https://dpdk.org/browse/dpdk-stable/
>
> Hi Luca,
> while my tests won't achieve the coverage of the bigger labs I still
> wanted to mention
> that I've built this for Ubuntu 21.04 and successfully ran some
> OVS-DPDK based tests on it.
>
> 1.0.0 (07:05:12): phys (BM) tests
> 1.1.0 (07:05:12): initialize environment
> 1.1.1 (07:09:32): testpmd => Pass
> 1.1.2 (07:11:12): check testpmd output => Pass
> 2.0.0 (07:11:12): prep virtual test environment
>
> 1.0.0 (07:14:14): virt tests
> 1.1.0 (07:14:14): initialize environment
> 3.0.0 (07:15:30): performance tests
> 3.1.0 (07:15:30): prep benchmarks
> 3.2.0 (07:15:51): performance tests
> 3.2.1 (07:16:01): test guest-openvswitch for OVS-5CPU => Pass
> 3.2.2 (07:35:44): test guest-dpdk-vhost-user-client-multiq for
> OVSDPDK-VUC => Pass
> 4.0.0 (07:57:11): VUC endurance checks
> 4.1.0 (07:57:11): prep VUC endurance tests
> 4.1.1 (08:12:38): start stop guests (client) => Pass
> 4.1.2 (09:25:59): add/remove ports (client) => Pass
> 4.2.0 (09:35:04): Final cleanup
>
> P.S. 3.2.1 is actually not a DPDK case, but used for e.g speed comparisons
Thank you!
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2021-02-25 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 15:09 [dpdk-stable] " luca.boccassi
2021-02-25 9:43 ` [dpdk-stable] [dpdk-dev] " Christian Ehrhardt
2021-02-25 10:14 ` Luca Boccassi [this message]
2021-02-25 13:00 ` [dpdk-stable] " Pei Zhang
2021-02-25 14:39 ` Luca Boccassi
2021-03-02 6:23 ` [dpdk-stable] [dpdk-dev] " Kalesh Anakkur Purayil
2021-03-02 10:29 ` Luca Boccassi
2021-03-02 10:52 ` Chen, BoX C
2021-03-02 11:27 ` Luca Boccassi
2021-03-03 1:57 ` Chen, BoX C
2021-03-07 14:48 ` [dpdk-stable] " Ali Alnubani
2021-03-08 10:12 ` Luca Boccassi
2021-03-09 10:36 ` Govindharajan, Hariprasad
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=943c21dac28bb70c4d5448066010aca820cc70f6.camel@debian.org \
--to=bluca@debian.org \
--cc=Abhishek.Marathe@microsoft.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hariprasad.govindharajan@intel.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=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--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).