From: Pei Zhang <pezhang@redhat.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
david.marchand@redhat.com, ktraynor@redhat.com,
maxime.coquelin@redhat.com
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 20.08-rc1
Date: Wed, 15 Jul 2020 04:01:27 -0400 (EDT) [thread overview]
Message-ID: <1936148714.34575256.1594800087875.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <2553672.smuk0Yhj5f@thomas>
Hello all,
Testing with dpdk 20.08-rc1 from Red Hat looks good.
We cover below 16 scenarios and and all get PASS on RHEL8 testing:
(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)PVP 1Q live migration testing: PASS
(10)PVP 1Q cross numa node live migration testing: PASS
(11)Guest with ovs+dpdk+vhost-user 1Q live migration testing: PASS
(12)Guest with ovs+dpdk+vhost-user 1Q live migration testing (2M): PASS
(13)Guest with ovs+dpdk+vhost-user 2Q live migration testing: PASS
(14) Allocate memory from the NUMA node which Virtio device locates: PASS
(15)Host PF + DPDK testing: PASS
(16)Host VF + DPDK testing: PASS
Versions:
kernel 4.18
qemu 5.0
dpdk: git://dpdk.org/dpdk master
git log -1
commit 466032ef8012a7fddd8dda986c5977e9341e3c35 (HEAD -> master, tag: v20.08-rc1, origin/releases, origin/master, origin/HEAD)
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Mon Jul 13 02:50:06 2020 +0200
version: 20.08-rc1
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
NICs: X540-AT2 NIC(ixgbe, 10G)
Best regards,
Pei
----- Original Message -----
From: "Thomas Monjalon" <thomas@monjalon.net>
To: announce@dpdk.org
Sent: Monday, July 13, 2020 8:58:30 AM
Subject: [dpdk-dev] [dpdk-announce] release candidate 20.08-rc1
A new DPDK release candidate is ready for testing:
https://git.dpdk.org/dpdk/tag/?id=v20.08-rc1
There are 778 new patches in this snapshot.
Release notes:
https://doc.dpdk.org/guides/rel_notes/release_20_08.html
Highlights of 20.08-rc1, grouped by category:
* General
- external thread registration API
- bit operations API for drivers
- VFIO PF with VF token
* Networking
- eCPRI offload with flow API
- Tx scheduling offload
* Cryptography
- crypto-CRC chained operation for DOCSIS protocol
* RegEx
- new device class API for future RegEx drivers
* Tools
- testpmd 5-tuple swap for L2/L3/L4
- performance test application for flow rules
- l2fwd forwarding between asymmetric ports
We must complete this release cycle in the beginning of August.
DPDK 20.08-rc2 is expected in one week on July 20.
Please test and report issues on bugs.dpdk.org.
We should publish the roadmap for DPDK 20.11 now.
Thank you everyone
prev parent reply other threads:[~2020-07-15 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 0:58 Thomas Monjalon
2020-07-15 8:01 ` 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=1936148714.34575256.1594800087875.JavaMail.zimbra@redhat.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).