DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pei Zhang <pezhang@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: David Marchand <david.marchand@redhat.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	 Kevin Traynor <ktraynor@redhat.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.08-rc1
Date: Mon, 26 Jul 2021 21:05:13 +0800	[thread overview]
Message-ID: <CAMp7QknVmK3xwwnXmdEy55mtySBOxCze_JJuNGJk=ZFVKX1LqQ@mail.gmail.com> (raw)
In-Reply-To: <2166990.b960dYtlEj@thomas>

Hello Thomas,

The testing with dpdk 21.08 latest commit(newer than dpdk 21.08-rc1) from
Red Hat looks good. We tested below 19 scenarios 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 postcopy live migration testing: PASS
(14)Guest with ovs+dpdk+vhost-user 1Q live migration testing (2M): PASS
(15)Guest with ovs+dpdk+vhost-user 2Q live migration testing: PASS
(16)Guest with ovs+dpdk+vhost-user 2Q postcopy live migration testing: PASS
(17)Guest with ovs+dpdk+vhost-user 4Q live migration testing: PASS
(18)Host PF + DPDK testing: PASS
(19)Host VF + DPDK testing: PASS

Versions:

kernel 4.18
qemu 6.0

dpdk: git://dpdk.org/dpdk
# # git log -1
commit 73b91412ca5f7c5d1bb97e6fcc608afed19b25ef (HEAD -> main, origin/main,
origin/HEAD)
Author: Ivan Malov <ivan.malov@oktetlabs.ru>
Date:   Wed Jul 21 07:15:05 2021 +0300

    net/sfc: improve logging in MAE backend of flow API

    Errors detected during parsing of pattern items and actions
    are reflected by setting RTE error, but the name of the bad
    element is not disclosed, thus leaving the user to join the
    dots themselves. Adjust the code to log missing information.

    Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
    Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
    Reviewed-by: Andy Moreton <amoreton@xilinx.com>

# git branch
* main

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

Thanks.

Best regards,

Pei

On Sat, Jul 10, 2021 at 6:05 PM Thomas Monjalon <thomas@monjalon.net> wrote:

> A new DPDK release candidate is ready for testing:
>         https://git.dpdk.org/dpdk/tag/?id=v21.08-rc1
>
> There are 517 new patches in this snapshot.
> This release cycle is short and should be small.
>
> Release notes:
>         https://doc.dpdk.org/guides/rel_notes/release_21_08.html
>
> Highlights of 21.08-rc1:
>         - Linux auxiliary bus
>         - Aarch32 cross-compilation
>         - Arm CPPC power management
>         - Rx multi-queue monitoring for power management
>         - XZ compressed firmware read
>         - Marvell CNXK drivers for ethernet, crypto and baseband PHY
>
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 21.08-rc2 is expected in less than two weeks.
>
> Thank you everyone
>
>
>

      parent reply	other threads:[~2021-07-26 13:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-10 10:05 Thomas Monjalon
2021-07-21 10:56 ` Jiang, YuX
2021-07-21 11:31 ` Kalesh Anakkur Purayil
2021-07-21 21:16 ` Thinh Tran
2021-07-26 13:05 ` 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='CAMp7QknVmK3xwwnXmdEy55mtySBOxCze_JJuNGJk=ZFVKX1LqQ@mail.gmail.com' \
    --to=pezhang@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --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).