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 146CBA0548 for ; Mon, 14 Jun 2021 07:20:39 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B069540E50; Mon, 14 Jun 2021 07:20:37 +0200 (CEST) Received: from youngberry.canonical.com (youngberry.canonical.com [91.189.89.112]) by mails.dpdk.org (Postfix) with ESMTP id BCA764003E for ; Mon, 14 Jun 2021 07:20:35 +0200 (CEST) Received: from mail-qt1-f200.google.com ([209.85.160.200]) by youngberry.canonical.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1lsf1V-0000Ku-KB for stable@dpdk.org; Mon, 14 Jun 2021 05:20:34 +0000 Received: by mail-qt1-f200.google.com with SMTP id a12-20020ac8108c0000b029023c90fba3dcso6824980qtj.7 for ; Sun, 13 Jun 2021 22:20:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=9MYr5B5m2gbGz8P7DzqWn/nrrpbMQ0urYfEv5vJkSvc=; b=bP1TB0Ghn0MI7Pt9m4P++24BUaF0Z5Q/cT+m5n2piHMkGZ5gb9rIJboEY86xoLPPRC ysqvRMA0KDTf0PUrg7Tcp86OozkXSHgatvRQ5ab42eoIuThexn5DZrqEYXZHKE5h/NyP CbIbvTxTQt1Mp9OlGU0rcFV32A7GsS3v0qH+Uj24Acyy3YEQQ6hD5EGLC3JkqME1GtPs JClxOc3u/iHp8akW25zpNgigD1qw0edgstv+zo32DmVti5vAVqPqHQMsHYIEOC9xeJc1 owTMYVP4RSChCW+wOm2sj/pvk8sMVbjSQMNWZC9Q86mVNlhaue1xdYN4NTqj+iU7sWIt 7M9Q== X-Gm-Message-State: AOAM533PADTQtPs6g/1QggwQ0V71UcpeG63S/SQOwLhM11BUkXgQ2EK/ KDDalntBsO9cUgByOmbwcIN/a0alCiddGK3f4scElS6G7Q9zBuT40r94oprEnvEDrCJQqrep/eP a07pG2lNgqD6scfebxPKu8JgidhUM8BWDHwBrILe9 X-Received: by 2002:a05:620a:1249:: with SMTP id a9mr14743533qkl.114.1623648032735; Sun, 13 Jun 2021 22:20:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx5NRIVlqdUhIeqMOSY7hh2CHOalMqmTFfaTF+SyH9eHsfQBuADk0OUth5oHelhSReo542GSWyDiW3SbJYs/JY= X-Received: by 2002:a05:620a:1249:: with SMTP id a9mr14743509qkl.114.1623648032500; Sun, 13 Jun 2021 22:20:32 -0700 (PDT) MIME-Version: 1.0 References: <20210604055236.2900938-1-christian.ehrhardt@canonical.com> In-Reply-To: From: Christian Ehrhardt Date: Mon, 14 Jun 2021 07:20:06 +0200 Message-ID: To: "Jiang, YuX" , Luc Pelletier Cc: Kevin Traynor , Ali Alnubani , dpdk stable , dev , Abhishek Marathe , Akhil Goyal , "Walker, Benjamin" , David Christensen , "Govindharajan, Hariprasad" , Hemant Agrawal , "Stokes, Ian" , Jerin Jacob , "Mcnamara, John" , Ju-Hyoung Lee , Luca Boccassi , Pei Zhang , "Yu, PingX" , "Xu, Qian Q" , Raslan Darawsheh , NBU-Contact-Thomas Monjalon , "Peng, Yuan" , "Chen, Zhaoyan" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-stable] [dpdk-dev] 19.11.9 patches review and test - V2 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 Sender: "stable" On Fri, Jun 11, 2021 at 10:55 AM Jiang, YuX wrote: > > Hi Christian, > > Testing with dpdk v19.11.9-rc2 from Intel is almost finished, some build = issues and telemetry issue are found. Thank you for completing this on -rc2 and thereby giving us a preview of the final results. > # Basic Intel(R) NIC testing > * PF(i40e, ixgbe): test scenarios including rte_flow/TSO/Jumboframe/check= sum offload/Tunnel, etc. Listed but not all. > - Known issues as below: > 1) https://bugs.dpdk.org/show_bug.cgi?id=3D731 =E2=80=93 [dpdk-19= .11.9] telemetry: python3 /root/dpdk/usertools/dpdk-telemetry-client.py pro= mpt connection refused) > Fixed commit is af68c1d699be6c369e296b775bdbf13ae18b79cc= eal: fix hang in control thread creation This one was in the candidate list of patches for 19.11.x, but it didn't apply cleanly. I've asked for a backport in my mail on 20th May - in this thread [1] But in the meantime that was all done and -rc2 that you have tested contain= s 34cc55cce6b1 ("eal: fix race in control thread creation") af68c1d699be ("eal: fix hang in control thread creation") In the form of these backports: $ git tag --contains 555da24882e1ca836f9532304f5f58034e57ff5e v19.11.9-rc2 $ git tag --contains 0b8f4f0462f2260fc618e297e91317a891c6d255 v19.11.9-rc2 So if af68c1d699be really was meant to fix this known issue then it does not do so in 19.11.x. @Luc - I'm setting you to CC in case you happen to know why. > 2) https://bugs.dpdk.org/show_bug.cgi?id=3D687: unit_tests_power/= power_cpufreq: unit test failed. This issue is found in 21.05 and dev has p= atches to fix it but not merged into main. Ok, so hopefully this will eventually be fixed in 21.08 and then also in the respective 19.11.x afterwards. > * VF(i40e,ixgbe): test scenarios including vf-rte_flow/TSO/Jumboframe/che= cksum offload/Tunnel, Listed but not all. - No new issues are found. > * PF/VF(ice): test scenarios including switch features/Flow Director/Adva= nced RSS/ACL/DCF/Flexible Descriptor and so on, Listed but not all. > - One 4 known issues is found, but won't fix on LTS19.11. [dpdk-1= 9.11.7] userspace_ethtool/retrieve_eeprom: Dumped eeprom not same as linux = dumped. Fixed patches are based on 4 ice share code, not be contained in LT= S19.11. > * Build or compile: > * Build: cover the build test combination with different GCC/Clan= g and the popular OS revision such as Ubuntu20.04, CentOS8.3=EF=BC=8C SUSE1= 5, Fedora34 and so on. Listed but not all. > - Two new issues are found > 1) https://bugs.dpdk.org/show_bug.cgi?id=3D732 [dpdk-19.1= 1.9-rc2] DPDK build failed on Win10 > 2) https://bugs.dpdk.org/show_bug.cgi?id=3D728 [dpdk-19.1= 1.9-rc2]When compiling dpdk with make or meson under SUSE Linux Enterprise = Server 15 SP2, the compilation fails Known - currently we have to decide if we break SP3 (no change) or fix SP3 but thereby break SP2 (that is what was in -rc2). DIscussions and mail threads are ongoing, Ferruh and I tried to pull in Suse people as well since it all started with a kernel change backport. > - Known issue is Fedora34 GCC11 and Clang12 build issue > a.GCC11 issue is same as https://bugs.dpdk.org/show_bug.c= gi?id=3D692 : Bug 692 - bnx2x build fail on Fedora 34 with gcc 11. This iss= ue is found in 21.05 with Fedora34 GCC 11. Has patches to fix in 21.05 and = merged into main. > Applies below tree patches can build passed. Patc= hes link: > [v3,1/4] net/bnx2x: fix build with gcc11 = - Patchwork (dpdk.org) > [v3,2/4] net/bnx2x: fix build with gcc11 = - Patchwork (dpdk.org) > test/table: fix build with GCC 11 - Patch= work (dpdk.org) > b.Clang12 issue: app/test/dpdk-test.p/test_cmdline_num.c.= o build failed on Fedora34 with Clang12. > Fixed commits are 5ac070cfed test/cmdline: silenc= e clang 12 warning & 414245bbc5 test/cmdline: fix inputs array(Refer to K= evin's reply) Thanks for confirming, the coming -rc3 (still a while to give everone a chance for more backports) will have those fixed. If anyone needs it asap, it already is in the WIP branch on https://github.com/cpaelzer/dpdk-stable-queue/commits/19.11 > * Intel NIC single core/NIC performance: test scenarios including PF/VF s= ingle core performance test(AVX2+AVX512) test and so on. Listed but not all= . - All passed. No big data drop. > > # Basic cryptodev and virtio testing > * Virtio: both function and performance test are covered. Such as PVP/Vir= tio_loopback/virtio-user loopback/virtio-net VM2VM perf testing, etc.. List= ed but not all. > - One known issues about The UDP fragmentation offload feature of= Virtio-net device can=E2=80=99t be turned on in the VM, kernel issue, bugz= illa has been submited: https://bugzilla.kernel.org/show_bug.cgi?id=3D20707= 5, not fixed yet. > * Cryptodev: > - Function test: test scenarios including Cryptodev API testing/C= ompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc. Listed but not all. - All = passed. > - Performance test: test scenarios including Thoughput Performanc= e /Cryptodev Latency, etc. Listed but not all. - No big data drop. > > Best regards, > Yu Jiang > > >-----Original Message----- > >From: dev On Behalf Of Christian Ehrhardt > >Sent: Thursday, June 10, 2021 9:57 PM > >To: Kevin Traynor > >Cc: Ali Alnubani ; dpdk stable ; de= v > >; Abhishek Marathe ; > >Akhil Goyal ; Walker, Benjamin > >; David Christensen ; > >Govindharajan, Hariprasad ; Hemant > >Agrawal ; Stokes, Ian ; > >Jerin Jacob ; Mcnamara, John > >; Ju-Hyoung Lee ; Luca > >Boccassi ; Pei Zhang ; Yu, PingX > >; Xu, Qian Q ; Raslan Darawsheh > >; NBU-Contact-Thomas Monjalon > >; Peng, Yuan ; Chen, > >Zhaoyan > >Subject: Re: [dpdk-dev] 19.11.9 patches review and test - V2 > > > >On Thu, Jun 10, 2021 at 1:03 PM Kevin Traynor wrot= e: > >> > >> On 10/06/2021 11:29, Kevin Traynor wrote: > >> > On 10/06/2021 11:05, Christian Ehrhardt wrote: > >> >> On Thu, Jun 10, 2021 at 11:05 AM Ali Alnubani > >wrote: > >> >>> > >> >>> Hi Christian, > >> >>> > >> >>>> -----Original Message----- > >> >>>> From: Christian Ehrhardt > >> >>>> Sent: Thursday, June 10, 2021 11:49 AM > >> >>>> To: dpdk stable > >> >>>> Cc: dev ; Abhishek Marathe > >> >>>> ; Akhil Goyal > >> >>>> ; Ali Alnubani ; Walker, > >> >>>> Benjamin ; David Christensen > >> >>>> ; Govindharajan, Hariprasad > >> >>>> ; Hemant Agrawal > >> >>>> ; Ian Stokes ; > >> >>>> Jerin Jacob ; John McNamara > >> >>>> ; Ju-Hyoung Lee > >; > >> >>>> Kevin Traynor ; Luca Boccassi > >> >>>> ; Pei Zhang ; Yu, PingX > >> >>>> ; Xu, Qian Q ; Raslan > >> >>>> Darawsheh ; NBU- Contact-Thomas Monjalon > >> >>>> ; Peng, Yuan ; Chen, > >> >>>> Zhaoyan > >> >>>> Subject: Re: [dpdk-dev] 19.11.9 patches review and test - V2 > >> >>>> > >> >>>> On Fri, Jun 4, 2021 at 7:52 AM Christian Ehrhardt > >> >>>> wrote: > >> >>>>> > >> >>>>> Hi all, > >> >>>>> > >> >>>>> Here is version 2 of the list of patches targeted for stable rel= ease > >19.11.9. > >> >>>>> Thanks to plenty of helpful developers we've collected a few > >> >>>>> more backports by now and sorted out a few rare compile time > >> >>>>> issues that were > >> >>>> found with -rc1. > >> >>>>> > >> >>>>> The planned date for the final release of 19.11.9 is now 18th of= June. > >> >>>>> > >> >>>>> 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 t= o the > >release notes. > >> >>>>> > >> >>>>> A release candidate tarball can be found at: > >> >>>>> > >> >>>>> https://dpdk.org/browse/dpdk-stable/tag/?id=3Dv19.11.9-rc2 > >> >>>> > >> >>>> Unfortunately there were further build issues with new suse kerne= ls. > >> >>>> The fix for some of them, now breaks others :-/ The final fix > >> >>>> didn't finalize yet, but as a TL;DR it means there will be a -rc3= down the > >road. > >> >>>> > >> >>>> I beg your pardon for the extra work. > >> >>>> If you are testing non-suse and are already deep into the tests > >> >>>> you likely can continue that. > >> >>>> If you didn't start your tests yet then I'd recommend holding > >> >>>> back until -rc3 exists. > >> >>>> > >> >>> > >> >>> I see some build failures with gcc 11. Do we expect this release t= o > >support it? > >> >> > >> >> I have added all that were targeted at stable@dpdk, but I remember > >> >> that Kevin mentioned a few missing in 20.11.x due to the > >> >> submissions missing to go to stable@dpdk. > >> >> The same could be the case here. > >> >> @Kevin could you have a look at 19.11 and if there are some missing > >> >> point me to the commits to pick up? > >> >> > >> >> @Ali - if you have a particular bug signature that might help to > >> >> identify the right patch. > >> >> > >> > > >> > They will all note 'GCC' (or gcc) in the commit msg. Most will have > >> > an example of the 'warning' they resolved too. There was also > >> > bugzillas opened for them all i think, which note the fixing commit. > >> > So if you find any issues when building, you could cross-reference > >> > between warning in commit/warning in Bz and fixing commit. Of course > >> > there may be some new issues pop up in older code that was later > >changed/replaced in main. > >> > > >> > There was also 2 commits needed for clang 12 support (my bad for > >> > missing tags on these). > >> > >> > 5ac070cfed test/cmdline: silence clang 12 warning > >> ^ just sent backport of this with upstream commit and correct tag > >> http://inbox.dpdk.org/stable/20210610110028.230803-1-ktraynor@redhat.c > >> om/T/#u > > > >I've already applied it a few hours ago, but the content is the same > > > >> > 414245bbc5 test/cmdline: fix inputs array > >> ^ this one was already merged on 19.11 and 20.11 branches > > > >Yes, as are all the other GCC 11 fixes we discussed. > > > >Thank you Kevin! > > > >> > > >> >>> I also see some doxygen errors with version 1.9.1 in Fedora Rawhid= e. > >Will open a Bugzilla ticket. > >> >> > >> >> Rawhide builds of 19.11.x were broken for a while now, but yeah > >> >> filing the bug surely is the right path. > >> >> > >> >>> Thanks, > >> >>> Ali > >> >> > >> >> > >> >> > >> > > >> > > > > > >-- > >Christian Ehrhardt > >Staff Engineer, Ubuntu Server > >Canonical Ltd --=20 Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd