patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dpdk stable <stable@dpdk.org>, dev <dev@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 20.11.5 patches review and test
Date: Thu, 31 Mar 2022 13:55:39 +0100	[thread overview]
Message-ID: <CAMw=ZnS_1DANSiv6_ukEesT4aVi=k1Ljvg5dAaOsZfjWft4YBw@mail.gmail.com> (raw)
In-Reply-To: <CAATJJ0KHOx55N50hMz3xS1-mNFhwdctPe=Hz6yMmZguf8V17jw@mail.gmail.com>

On Thu, 31 Mar 2022 at 11:51, Christian Ehrhardt
<christian.ehrhardt@canonical.com> wrote:
>
>
>
> On Mon, Mar 28, 2022 at 5:29 PM Luca Boccassi <bluca@debian.org> wrote:
>>
>> On Mon, 2022-03-28 at 14:55 +0200, Christian Ehrhardt wrote:
>> >
>> >
>> > On Mon, Mar 28, 2022 at 1:50 PM Luca Boccassi <bluca@debian.org>
>> > wrote:
>> > > On Mon, 2022-03-28 at 09:40 +0200, Christian Ehrhardt wrote:
>> > > > On Fri, Mar 18, 2022 at 4:21 PM <luca.boccassi@gmail.com> wrote:
>> > > > >
>> > > > > Hi all,
>> > > > >
>> > > > > Here is a list of patches targeted for stable release 20.11.5.
>> > > >
>> > > > Hi Luca,
>> > > > this backport
>> > > >
>> > > https://git.dpdk.org/dpdk-stable/commit/?h=20.11&id=64452c878f225c147dfb7156e605f5b55da9f7c0
>> > > > Causes symbol changes
>> > > >
>> > > https://launchpadlibrarian.net/593478119/buildlog_ubuntu-impish-amd64.dpdk_20.11.5~rc1-0ubuntu0.21.10.1~impishppa1_BUILDING.txt.gz
>> > > >
>> > > > There is an exception mentioned for 21.11, but would this also
>> > > apply
>> > > > for 20.11 or should we keep it stable there?
>> > >
>> > > Thanks for the heads-up, these looked like additions to the map
>> > > file so
>> > > I overlooked them. I'll revert this in the 20.11 tree, I don't
>> > > think we
>> > > should change symbols there.
>> > >
>> >
>> >
>> > Thanks, this breaks my test builds - will there be an RC2 with it or
>> > shall I just revert it in-place for now?
>>
>> Revert in place please - I don't think I'll do an RC2 just for this, as
>> that would trigger more tests, and it's a build issue mostly.
>
>
> With that revert in place it built and also tested fine in the HW and Scenarios that I have
>
> 1.0.0 (06:05:54): phys (BM) tests
>   1.1.0 (06:05:54): initialize environment
>     1.1.1 (06:11:08): testpmd  => Pass
>     1.1.2 (06:12:47): check testpmd output  => Pass
> 2.0.0 (06:12:47): prep virtual test environment
>
> 1.0.0 (06:15:50): virt tests
>   1.1.0 (06:15:50): initialize environment
> 3.0.0 (06:17:08): performance tests
>   3.1.0 (06:17:08): prep benchmarks
>   3.2.0 (06:17:30): performance tests
>     3.2.1 (06:17:57): test guest-openvswitch for OVS-5CPU  => Pass
>     3.2.2 (06:38:24): test guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC  => Pass
> 4.0.0 (06:59:51): VUC endurance checks
>   4.1.0 (06:59:51): prep VUC endurance tests
>     4.1.1 (07:19:20): start stop guests (client)  => Pass
>     4.1.2 (08:33:39): add/remove ports (client)  => Pass
>
> That is the same set of tests as in the past, so if you want a more readable version for the docs you can use that of last time and or look in the 19.11.x series where I had them.

Thank you, added to the list

  reply	other threads:[~2022-03-31 12:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 15:20 luca.boccassi
2022-03-23 13:33 ` Pei Zhang
2022-03-23 15:36   ` Luca Boccassi
2022-03-28  7:40 ` Christian Ehrhardt
2022-03-28 11:50   ` Luca Boccassi
2022-03-28 12:55     ` Christian Ehrhardt
2022-03-28 15:29       ` Luca Boccassi
2022-03-31 10:50         ` Christian Ehrhardt
2022-03-31 12:55           ` Luca Boccassi [this message]
2022-03-29 11:48 ` Jiang, YuX
2022-03-29 12:12   ` Luca Boccassi
2022-03-30 10:01   ` Jiang, YuX
2022-03-30  8:22 ` Ali Alnubani

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='CAMw=ZnS_1DANSiv6_ukEesT4aVi=k1Ljvg5dAaOsZfjWft4YBw@mail.gmail.com' \
    --to=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).