patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Luca Boccassi <luca.boccassi@gmail.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>,
	John McNamara <john.mcnamara@intel.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: RE: 20.11.8 patches review and test
Date: Wed, 19 Apr 2023 13:10:53 +0000	[thread overview]
Message-ID: <DM4PR12MB5167DF69ECE28B20151C262FDA629@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAMw=ZnSPtbdQfn_5c0Mzw+KQA+JKOmO5p+S0oczGEj-M72x_1Q@mail.gmail.com>

> -----Original Message-----
> From: Luca Boccassi <luca.boccassi@gmail.com>
> Sent: Wednesday, April 19, 2023 4:02 PM
> To: Ali Alnubani <alialnu@nvidia.com>
> Cc: stable@dpdk.org; dev@dpdk.org; John McNamara
> <john.mcnamara@intel.com>; Kevin Traynor <ktraynor@redhat.com>;
> Raslan Darawsheh <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon
> (EXTERNAL) <thomas@monjalon.net>
> Subject: Re: 20.11.8 patches review and test
> 
> On Wed, 19 Apr 2023 at 10:22, Ali Alnubani <alialnu@nvidia.com> wrote:
> >
> > > -----Original Message-----
> > > From: Ali Alnubani <alialnu@nvidia.com>
> > > Sent: Wednesday, April 12, 2023 6:15 PM
> > > To: luca.boccassi@gmail.com; stable@dpdk.org
> > > Cc: dev@dpdk.org; Abhishek Marathe
> <Abhishek.Marathe@microsoft.com>;
> > > benjamin.walker@intel.com; David Christensen
> <drc@linux.vnet.ibm.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>; Luca Boccassi
> <bluca@debian.org>;
> > > Pei Zhang <pezhang@redhat.com>; qian.q.xu@intel.com; Raslan
> Darawsheh
> > > <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> > > <thomas@monjalon.net>; Yanghang Liu <yanghliu@redhat.com>;
> > > yuan.peng@intel.com; zhaoyan.chen@intel.com
> > > Subject: RE: 20.11.8 patches review and test
> > >
> > > > -----Original Message-----
> > > > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > > > Sent: Friday, March 31, 2023 9:20 PM
> > > > To: stable@dpdk.org
> > > > Cc: 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>; 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>; Luca Boccassi <bluca@debian.org>; Pei Zhang
> > > > <pezhang@redhat.com>; qian.q.xu@intel.com; Raslan Darawsheh
> > > > <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> > > > <thomas@monjalon.net>; Yanghang Liu <yanghliu@redhat.com>;
> > > > yuan.peng@intel.com; zhaoyan.chen@intel.com
> > > > Subject: 20.11.8 patches review and test
> > > >
> > > > Hi all,
> > > >
> > > > Here is a list of patches targeted for stable release 20.11.8.
> > > >
> > > > The planned date for the final release is April 17th.
> > > >
> > > > 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.8-rc1
> > > >
> > > > These patches are located at branch 20.11 of dpdk-stable repo:
> > > >     https://dpdk.org/browse/dpdk-stable/
> > > >
> > > > Thanks.
> > > >
> > > > Luca Boccassi
> > > >
> > > > ---
> > >
> > > Hello,
> > >
> > > We ran the following functional tests with Nvidia hardware on v20.11.8-
> rc1:
> > > - Basic functionality:
> > >   Send and receive multiple types of traffic.
> > > - testpmd xstats counter test.
> > > - testpmd timestamp test.
> > > - Changing/checking link status through testpmd.
> > > - rte_flow tests.
> > > - Some RSS tests.
> > > - VLAN filtering, stripping and insertion tests.
> > > - Checksum and TSO tests.
> > > - ptype tests.
> > > - link_status_interrupt example application tests.
> > > - l3fwd-power example application tests.
> > > - Multi-process example applications tests.
> > > - Hardware LRO tests.
> > >
> > > Functional tests ran on:
> > > - NIC: ConnectX-6 Dx / OS: Ubuntu 20.04 / Driver: MLNX_OFED_LINUX-
> 5.9-
> > > 0.5.6.0 / Firmware: 22.36.1010
> > > - NIC: ConnectX-7 / OS: Ubuntu 20.04 / Driver: MLNX_OFED_LINUX-5.9-
> > > 0.5.6.0 / Firmware: 22.36.1010
> > > - DPU: BlueField-2 / DOCA SW version: 1.5.1 / Firmware: 24.35.2000
> > >
> > > Additionally, we ran compilation tests with multiple configurations in the
> > > following OS/driver combinations:
> > > - Ubuntu 20.04.5 with MLNX_OFED_LINUX-5.9-0.5.6.0.
> > > - Ubuntu 20.04.5 with rdma-core master (f0a079f).
> > > - Ubuntu 20.04.5 with rdma-core v28.0.
> > > - Ubuntu 18.04.6 with rdma-core v17.1.
> > > - Ubuntu 18.04.6 with rdma-core master (f0a079f) (i386).
> > > - Fedora 37 with rdma-core v41.0.
> > > - Fedora 39 (Rawhide) with rdma-core v44.0.
> > > - CentOS 7 7.9.2009 with rdma-core master (f0a079f).
> > > - CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.9-0.5.6.0.
> > > - CentOS 8 8.4.2105 with rdma-core master (f0a079f).
> > > - OpenSUSE Leap 15.4 with rdma-core v38.1.
> > > - Windows Server 2019 with Clang 11.0.0.
> > >
> > > We don't see new issues caused by the changes in this release.
> > >
> > > Please note that not all the functional tests mentioned above fall under
> > > "Basic functionality with testpmd" like reported in the release notes for
> > > previous releases:
> > > https://git.dpdk.org/dpdk-
> > >
> stable/commit/?h=v20.11.7&id=62865fef48cb93042e8b9f85821eb02e1031e8f
> > > 0
> > > Some of them test other applications.
> > >
> > > Thanks,
> > > Ali
> >
> > Hello,
> >
> > I see this documentation build failure on Fedora 37:
> >
> > $ ninja-build -C build doc
> > [..]
> > [2/4] Generating doc/api/doxygen with a custom command
> > FAILED: doc/api/html
> > /root/dpdk/doc/api/generate_doxygen.sh doc/api/doxy-api.conf
> doc/api/html /root/dpdk/doc/api/doxy-html-custom.sh
> > /root/dpdk/lib/librte_cryptodev/rte_cryptodev_pmd.h:489: error: found
> documented return type for rte_cryptodev_pmd_callback_process that
> does not return anything (warning treated as error, aborting now)
> > [..]
> > ninja: build stopped: subcommand failed.
> 
> I cannot reproduce this on Debian. Does it start working again if you
> revert commit 6500e9e4d8d556a3d29c26b5fe2c9d5f2c6acd1a ?

It doesn't reproduce for me on Ubuntu 20.04.
Reverting the commit you pointed to doesn't resolve it. I see now that it reproduces on 20.11.7 as well.

Meson: 1.0.1
Doxygen: 1.9.5

  reply	other threads:[~2023-04-19 13:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 18:20 luca.boccassi
2023-04-06  7:19 ` Xu, HailinX
2023-04-11  5:17   ` Xu, HailinX
2023-04-14 10:06     ` Luca Boccassi
2023-04-17 10:34       ` Xu, HailinX
2023-04-12 15:15 ` Ali Alnubani
2023-04-14  8:28   ` YangHang Liu
2023-04-19  9:22   ` Ali Alnubani
2023-04-19 13:02     ` Luca Boccassi
2023-04-19 13:10       ` Ali Alnubani [this message]
2023-04-19 13:11     ` David Marchand
2023-04-19 13:14       ` Ali Alnubani
2023-04-19 13:24         ` David Marchand
2023-04-19 14:14           ` Luca Boccassi
2023-04-19 14:23             ` Ali Alnubani
2023-04-19 14:26               ` Kevin Traynor
2023-04-19 14:30                 ` Luca Boccassi
2023-04-19 14:35                   ` Ali Alnubani
2023-04-19 14:35                   ` David Marchand
2023-04-19 14:38                     ` Luca Boccassi

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=DM4PR12MB5167DF69ECE28B20151C262FDA629@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=luca.boccassi@gmail.com \
    --cc=rasland@nvidia.com \
    --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).