From: Kevin Traynor <ktraynor@redhat.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: stable@dpdk.org, 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>,
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>,
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>,
yuan.peng@intel.com, zhaoyan.chen@intel.com
Subject: Re: 21.11.1 patches review and test
Date: Mon, 25 Apr 2022 14:39:23 +0100 [thread overview]
Message-ID: <cb904091-db04-79ca-5a7a-5ad8b60d5533@redhat.com> (raw)
In-Reply-To: <CAATJJ0Kme4977eZe3QO+2=fVQa_Zt4Uka6yL-=gQi6+8TrOacg@mail.gmail.com>
On 20/04/2022 06:50, Christian Ehrhardt wrote:
> On Fri, Apr 1, 2022 at 12:22 PM Kevin Traynor<ktraynor@redhat.com> wrote:
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.1.
>>
>> Please try and complete validation by April 13th.
>>
>> 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.1-rc1
>>
>> These patches are located at branch 21.11 of dpdk-stable repo:
>> https://dpdk.org/browse/dpdk-stable/
> Hi Kevin,
> now that the ABI change discussion has somewhat settled I have run the
> tests ignoring the symbols changes for now.
> All LGTM on Ubuntu 22.04 + OVS 2.17 + DPDK 21.11.1-rc1
>
> 1.0.0 (11:42:53): phys (BM) tests
> 1.1.0 (11:42:53): initialize environment
> 1.1.1 (11:44:54): testpmd => Pass
> 1.1.2 (11:45:43): check testpmd output => Pass
> 2.0.0 (11:45:43): prep virtual test environment
>
> 1.0.0 (11:48:05): virt tests
> 1.1.0 (11:48:05): initialize environment
> 3.0.0 (11:49:30): performance tests
> 3.1.0 (11:49:30): prep benchmarks
> 3.2.0 (11:49:51): performance tests
> 3.2.1 (11:50:02): test guest-openvswitch for OVS-5CPU => Pass
> 3.2.2 (12:09:30): test guest-dpdk-vhost-user-client-multiq for
> OVSDPDK-VUC => Pass
> 4.0.0 (12:28:54): VUC endurance checks
> 4.1.0 (12:28:54): prep VUC endurance tests
> 4.1.1 (12:41:59): start stop guests (client) => Pass
> 4.1.2 (13:48:30): add/remove ports (client) => Pass
> 4.2.0 (13:58:11): Final cleanup
>
> The above is kind of a high level test log, for the validation section
> of a stable release I usually use:
>
> * Build tests of DPDK & OVS 2.13.3 on Ubuntu 20.04 (meson based)
> * Functional and performance tests based on OVS-DPDK on x86_64
> * Autopkgtests for DPDK and OpenvSwitch
>
>
Thanks for the testing and Christian. I will add your summary to the
validation section.
prev parent reply other threads:[~2022-04-25 13:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 10:22 Kevin Traynor
2022-04-11 3:03 ` Pei Zhang
2022-04-13 4:06 ` YangHang Liu
2022-04-13 13:20 ` Kevin Traynor
2022-04-11 6:58 ` Christian Ehrhardt
2022-04-13 7:26 ` Christian Ehrhardt
2022-04-13 8:44 ` Kevin Traynor
2022-04-13 10:06 ` Kevin Traynor
2022-04-14 5:52 ` Christian Ehrhardt
2022-04-14 7:17 ` Thomas Monjalon
2022-04-14 9:08 ` Kevin Traynor
2022-04-11 11:00 ` Ali Alnubani
2022-04-13 13:18 ` Kevin Traynor
2022-04-12 8:58 ` Jiang, YuX
2022-04-13 13:19 ` Kevin Traynor
2022-04-14 4:58 ` Jiang, YuX
2022-04-25 15:01 ` Kevin Traynor
2022-04-20 5:50 ` Christian Ehrhardt
2022-04-25 13:39 ` 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=cb904091-db04-79ca-5a7a-5ad8b60d5533@redhat.com \
--to=ktraynor@redhat.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--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=pezhang@redhat.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).