DPDK patches and discussions
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: dpdk stable <stable@dpdk.org>
Cc: dev <dev@dpdk.org>,
	Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	 Akhil Goyal <akhil.goyal@nxp.com>,
	Ali Alnubani <alialnu@nvidia.com>,
	 "Walker, Benjamin" <benjamin.walker@intel.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	 "Govindharajan, Hariprasad" <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>,
	Kevin Traynor <ktraynor@redhat.com>,
	 Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
	"Yu, PingX" <pingx.yu@intel.com>,
	 "Xu, Qian Q" <qian.q.xu@intel.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	 Thomas Monjalon <thomas@monjalon.net>,
	"Peng, Yuan" <yuan.peng@intel.com>,
	 "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-dev] 19.11.8 patches review and test
Date: Mon, 12 Apr 2021 11:12:46 +0200
Message-ID: <CAATJJ0KnsLo-Hefm8AKBvpeN1NQbxgHkMhFaW=sEu=P1CWxgCw@mail.gmail.com> (raw)
In-Reply-To: <20210409074357.2499008-1-christian.ehrhardt@canonical.com>

On Fri, Apr 9, 2021 at 9:44 AM Christian Ehrhardt
<christian.ehrhardt@canonical.com> wrote:
> Hi all,
> Here is a list of patches targeted for stable release 19.11.8.
> The planned date for the final release is 16th April.
> 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.
> Note:
> This is a special interim release not following the releases of recent
> mainline (that was 19.11.7). Instead this addresses issues with >=19.11.6
> identified and discussed in:
>   http://mails.dpdk.org/archives/stable/2021-March/029418.html
> Testing-Note:
> The only changes this release has over the former one are about linking.
> We switch back to how it was <=19.11.6 since it regressed some use-cases.
> The most known one at the moment is building OVS 2.13 vs a DPDK that was
> built with meson. It seems that make-based DPDK builds are unaffected.
> Due to that this verification phase should not so much be about the usual
> performance, functionality, ... (I'm happy if you run those, but they are
> not strictly required). Instead the focus should mostly about buildability
> via the various possible combinations that exist.

I can confirm that with 19.11.8 the build of OpenVswitch vs a
meson-built DPDK works again.
Tested on OVS 2.13.3 vs DPDK 19.11.8-rc1 in Ubuntu 20.04 and 20.10 on
all supported
architectures (amd64,armhf,arm64 and ppc64el - the others
s390x/riscv64 don't have DPDK built).

> A release candidate tarball can be found at:
>     https://dpdk.org/browse/dpdk-stable/tag/?id=v19.11.8-rc1
> These patches are located at branch 19.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
> Thanks.
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
> Christian Ehrhardt (7):
>       Revert "Revert "Revert "build/pkg-config: prevent overlinking"""
>       Revert "Revert "Revert "build/pkg-config: improve static linking flags"""
>       Revert "Revert "Revert "build/pkg-config: output drivers first for static build"""
>       Revert "Revert "Revert "build/pkg-config: move pkg-config file creation"""
>       Revert "Revert "Revert "build: always link whole DPDK static libraries"""
>       Revert "Revert "Revert "devtools: test static linkage with pkg-config"""
>       Regenerate meson.build changes required due to reverts

Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

  reply	other threads:[~2021-04-12  9:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  7:43 Christian Ehrhardt
2021-04-12  9:12 ` Christian Ehrhardt [this message]
2021-04-14 10:25   ` Chen, BoX C
2021-04-13 12:11 ` Govindharajan, Hariprasad
2021-04-19  3:26 ` Pei Zhang

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAATJJ0KnsLo-Hefm8AKBvpeN1NQbxgHkMhFaW=sEu=P1CWxgCw@mail.gmail.com' \
    --to=christian.ehrhardt@canonical.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=akhil.goyal@nxp.com \
    --cc=alialnu@nvidia.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --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=ktraynor@redhat.com \
    --cc=pezhang@redhat.com \
    --cc=pingx.yu@intel.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 \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git