DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pei Zhang <pezhang@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, david.marchand@redhat.com, ktraynor@redhat.com,
	 maxime.coquelin@redhat.com, Chao Yang <chayang@redhat.com>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 20.08-rc3
Date: Thu, 6 Aug 2020 01:42:03 -0400 (EDT)	[thread overview]
Message-ID: <1469043228.37297254.1596692523337.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <11727811.Rr6YEUNczV@thomas>

Hello Thomas,

Testing with dpdk 20.08-rc3 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.1
dpdk: git://dpdk.org/dpdk master
# git log -1
commit 6636b04b82897816e0e05134f55a578cb7e124bc (HEAD -> master, tag: v20.08-rc3, origin/releases, origin/master, origin/HEAD)
Author: Thomas Monjalon <thomas@monjalon.net>
Date:   Fri Jul 31 01:37:05 2020 +0200

    version: 20.08-rc3
    
    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: Friday, July 31, 2020 7:59:31 AM
Subject: [dpdk-dev] [dpdk-announce] release candidate 20.08-rc3

A new DPDK release candidate is ready for testing:
	https://git.dpdk.org/dpdk/tag/?id=v20.08-rc3

There are 138 new patches in this snapshot.

Release notes:
	http://doc.dpdk.org/guides/rel_notes/release_20_08.html
A lot of deprecation notices are expected.

The -rc4 will include only critical bug fixes, doc and tooling.
You may share some release validation results
by replying to this message (at dev@dpdk.org).

Please share your roadmap for 20.11 so we can prioritize tasks.
Planning is especially important to avoid flooding maintainers.

Thank you everyone



      reply	other threads:[~2020-08-06  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 23:59 Thomas Monjalon
2020-08-06  5:42 ` 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=1469043228.37297254.1596692523337.JavaMail.zimbra@redhat.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).