From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 98715A0503 for ; Thu, 31 Mar 2022 14:55:54 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 890C4428F4; Thu, 31 Mar 2022 14:55:54 +0200 (CEST) Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com [209.85.167.48]) by mails.dpdk.org (Postfix) with ESMTP id 4C6D64014F; Thu, 31 Mar 2022 14:55:52 +0200 (CEST) Received: by mail-lf1-f48.google.com with SMTP id bq24so25382183lfb.5; Thu, 31 Mar 2022 05:55:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gCuofgsSRfEj1h3yqfRwn+TwtNvgqV5EdzfnEjgNGLQ=; b=jFlA2oQXO42793LQT1o1kOzKjWfGguN9FJNREaMjrh3T3qbz/QDMf1ctWbJ9YZBF+w dxDaQl1bO6yBAcz5bd7iNxznJYvMrZR/eCNudBXrpL+QXi+Vwp3rA9xjt0HGf6RsB62s i6IUsOUAKt8exI7Go8C6rPSleQ3izXi0XmRy1LJQ2rFYm93KykF+KVbocSDC73XUuEQe AaBFEj/oYjdnZ4PCzDXb27d/ihKkqNUGVl6mXdfdelficsZDN7sLxVlZMScwZvvL+QuP N65SX66RCmE7ZwOIxswiP+t4CiKeZYgmTyNcRpU8HydHxbkfULFc/hCFNbvir6wgQYam GeAg== X-Gm-Message-State: AOAM532U1A4r2I9n6HXgNJk+m1xCAw/j7JKevsupMJFAShUop+cN1U5u C+jKBfHdksQ791Cp/rZ3ujsyAggK4LGIGw== X-Google-Smtp-Source: ABdhPJw9Gpqy+Un1RJhUgXNGLbxlASJ5VJCKxaPSLpZF8lnhzHBrH8JIoxL0h93oaCRDMvhdgB0yPg== X-Received: by 2002:a05:6512:1585:b0:445:908b:ad71 with SMTP id bp5-20020a056512158500b00445908bad71mr10372609lfb.200.1648731351527; Thu, 31 Mar 2022 05:55:51 -0700 (PDT) Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com. [209.85.167.51]) by smtp.gmail.com with ESMTPSA id n4-20020a196f44000000b0044a38f193d6sm2660943lfk.207.2022.03.31.05.55.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 31 Mar 2022 05:55:51 -0700 (PDT) Received: by mail-lf1-f51.google.com with SMTP id e16so41282996lfc.13; Thu, 31 Mar 2022 05:55:51 -0700 (PDT) X-Received: by 2002:a05:6512:10c6:b0:44a:9dc4:22ee with SMTP id k6-20020a05651210c600b0044a9dc422eemr10498191lfg.581.1648731350951; Thu, 31 Mar 2022 05:55:50 -0700 (PDT) MIME-Version: 1.0 References: <20220318152058.1089525-1-luca.boccassi@gmail.com> <0ec94c4d87d437bd8298927c40c14340d22b18e3.camel@debian.org> In-Reply-To: From: Luca Boccassi Date: Thu, 31 Mar 2022 13:55:39 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: 20.11.5 patches review and test To: Christian Ehrhardt Cc: dpdk stable , dev , Thomas Monjalon Content-Type: text/plain; charset="UTF-8" X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org On Thu, 31 Mar 2022 at 11:51, Christian Ehrhardt wrote: > > > > On Mon, Mar 28, 2022 at 5:29 PM Luca Boccassi wrote: >> >> On Mon, 2022-03-28 at 14:55 +0200, Christian Ehrhardt wrote: >> > >> > >> > On Mon, Mar 28, 2022 at 1:50 PM Luca Boccassi >> > wrote: >> > > On Mon, 2022-03-28 at 09:40 +0200, Christian Ehrhardt wrote: >> > > > On Fri, Mar 18, 2022 at 4:21 PM 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