DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pei Zhang <pezhang@redhat.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: stable@dpdk.org, dev@dpdk.org,
	 Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	 Ali Alnubani <alialnu@nvidia.com>,
	benjamin.walker@intel.com,
	 David Christensen <drc@linux.vnet.ibm.com>,
	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>,
	pingx.yu@intel.com, "xu, qian" <qian.q.xu@intel.com>,
	 Raslan Darawsheh <rasland@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	yuan.peng@intel.com, "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-dev] 19.11.8 patches review and test
Date: Mon, 19 Apr 2021 11:26:11 +0800	[thread overview]
Message-ID: <CAMp7QknW+QGqrzSkM2WeJEOx+seZFsE9ec3BsC03efDq1ZR1Ew@mail.gmail.com> (raw)
In-Reply-To: <20210409074357.2499008-1-christian.ehrhardt@canonical.com>

Hi Christian,

The testing with dpdk 19.11.8-rc1 from Red Hat looks good. We tested below
16 scenarios and and all got PASS on RHEL8:

(1)Guest with device assignment(PF) throughput testing(1G hugepage size):
PASS
(2)Guest with device assignment(PF) throughput testing(2M hugepage size) :
PASS
(3)Guest with device assignment(VF) throughput testing: PASS
(4)PVP (host dpdk testpmd as vswitch) 1Q: throughput testing: PASS
(5)PVP vhost-user 2Q throughput testing: PASS
(6)PVP vhost-user 1Q - cross numa node throughput testing: PASS
(7)Guest with vhost-user 2 queues throughput testing: PASS
(8)vhost-user reconnect with dpdk-client, qemu-server: qemu reconnect: PASS
(9)vhost-user reconnect with dpdk-client, qemu-server: ovs reconnect: PASS
(10)PVP 1Q live migration testing: PASS
(11)PVP 1Q cross numa node live migration testing: PASS
(12)Guest with ovs+dpdk+vhost-user 1Q live migration testing: PASS
(13)Guest with ovs+dpdk+vhost-user 1Q live migration testing (2M): PASS
(14)Guest with ovs+dpdk+vhost-user 2Q live migration testing: PASS
(15)Host PF + DPDK testing: PASS
(16)Host VF + DPDK testing: PASS

Versions:

kernel 4.18
qemu 5.2

dpdk: git://dpdk.org/dpdk-stable
# git log -1
commit 6a1b35022ca0dbdfa04cb7b8bfa5694c2fdda3bc (HEAD, tag: v19.11.8-rc1,
origin/19.11)
Author: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date:   Thu Apr 8 16:55:20 2021 +0200

    version: 19.11.8-rc1

    Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>



# git branch
remotes/origin/19.11

NICs: X540-AT2 NIC(ixgbe, 10G)

Best regards,

Pei

On Fri, Apr 9, 2021 at 3:43 PM 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.
>
> 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
>
>

      parent reply	other threads:[~2021-04-19  3:26 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
2021-04-14 10:25   ` Chen, BoX C
2021-04-13 12:11 ` Govindharajan, Hariprasad
2021-04-19  3:26 ` Pei Zhang [this message]

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=CAMp7QknW+QGqrzSkM2WeJEOx+seZFsE9ec3BsC03efDq1ZR1Ew@mail.gmail.com \
    --to=pezhang@redhat.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=christian.ehrhardt@canonical.com \
    --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=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 \
    /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).