From: Pei Zhang <pezhang@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
David Marchand <david.marchand@redhat.com>,
Kevin Traynor <ktraynor@redhat.com>,
Chao Yang <chayang@redhat.com>
Subject: Re: release candidate 22.03-rc2
Date: Mon, 7 Mar 2022 21:55:08 +0800 [thread overview]
Message-ID: <CAMp7Qk=kxq5kPtCHg7b-NRD9=FrBOLrSgF9a1ttM9JrS_eqvGg@mail.gmail.com> (raw)
In-Reply-To: <825166309.0ifERbkFSE@thomas>
[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]
Hello Thomas,
The testing with dpdk 22.03-rc2 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 live migration testing (2M): PASS
(14)Guest with ovs+dpdk+vhost-user 2Q live migration testing: PASS
(15)Guest with ovs+dpdk+vhost-user 4Q live migration testing: PASS
(16)Host PF + DPDK testing: PASS
(17)Host VF + DPDK testing: PASS
(18)vDPA + host DPDK basic testing: PASS
(19)vDPA + VM DPDK basic testing: PASS
Versions:
kernel 4.18
qemu 6.2
dpdk: git://dpdk.org/dpdk
# git log -1
commit 305769000c40a4fdf1ed0cf24c157b447b91ea7d (HEAD -> main, tag:
v22.03-rc2, origin/main, origin/HEAD)
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Sun Feb 27 21:52:48 2022 +0100
version: 22.03-rc2
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
NICs: X540-AT2 NIC(ixgbe, 10G)
Best regards,
Pei
On Mon, Feb 28, 2022 at 5:02 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v22.03-rc2
>
> There are 306 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_22_03.html
>
> Highlights of 22.03-rc2:
> - ethdev flow API for templates and async operations
> - Marvell GPIO driver for CNXK
>
> The driver features should be frozen now.
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 22.03-rc3 is expected in one week.
>
> Thank you everyone
>
>
>
[-- Attachment #2: Type: text/html, Size: 3673 bytes --]
prev parent reply other threads:[~2022-03-07 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 21:02 Thomas Monjalon
2022-03-01 10:56 ` Jiang, YuX
2022-03-01 12:35 ` Thomas Monjalon
2022-03-01 14:41 ` Alexander Kozyrev
2022-03-03 4:13 ` Jiang, YuX
2022-03-04 12:03 ` Jiang, YuX
2022-03-03 17:54 ` Thinh Tran
2022-03-07 13:55 ` 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='CAMp7Qk=kxq5kPtCHg7b-NRD9=FrBOLrSgF9a1ttM9JrS_eqvGg@mail.gmail.com' \
--to=pezhang@redhat.com \
--cc=chayang@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).