All of lore.kernel.org
 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, Hekai Wang <hewang@redhat.com>,
	 Chao Yang <chayang@redhat.com>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 20.11-rc1
Date: Wed, 28 Oct 2020 23:45:29 -0400 (EDT)	[thread overview]
Message-ID: <62225691.5773307.1603943129372.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1695913.Ws3t40NQoN@thomas>

Hello Thomas,

Testing with dpdk 20.11-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.1
dpdk: git://dpdk.org/dpdk   

# git log -1
commit c3afd1cba69bd7a900fd63c02cc87fba8d74430a
...

# git branch
* main


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

Best regards,

Pei

----- Original Message -----
From: "Thomas Monjalon" <thomas@monjalon.net>
To: announce@dpdk.org
Sent: Wednesday, October 21, 2020 12:50:13 AM
Subject: [dpdk-dev] [dpdk-announce] release candidate 20.11-rc1

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

There are 1265 new patches in this snapshot, being the biggest -rc1 ever.
Like the previous LTS, the API of this -rc1 is exceptionnally not frozen.
More major changes are pending for -rc2.

Release notes:
	https://doc.dpdk.org/guides/rel_notes/release_20_11.html

Highlights of 20.11-rc1, grouped by category:
* General
	- write combining store API
	- prefetch with intention to write API
	- cldemote API
	- SIMD bitwidth limit API
	- Windows PCI netuio
	- moved igb_uio to dpdk-kmods/linux
	- removed Python 2 support
	- removed Make support
* Networking
	- CRC optimization for Intel AVX-512
	- FEC API
	- Rx buffer split
	- thread safety in flow API
	- shared action in flow API
	- flow sampling and mirroring
	- tunnel offload API
	- multi-port hairpin
	- Solarflare EF100 architecture
	- vhost-vDPA backend in virtio-user
	- removed vhost dequeue zero-copy
	- SWX pipeline aligned with P4
* Baseband
	- Intel ACC100 driver
* Cryptography
	- raw datapath API
	- Broadcom BCMFS symmetric crypto driver
* RegEx
	- Marvell OCTEON TX2 regex driver
* Others
	- ACL optimized for Intel AVX-512
	- Intel DSA support in IOAT driver

Please test and report issues on bugs.dpdk.org.
DPDK 20.11-rc2 is expected at the end of this month.
Let's be reactive and focus on this important milestone.

Thank you everyone



      reply	other threads:[~2020-10-29  3:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 16:50 [dpdk-dev] [dpdk-announce] release candidate 20.11-rc1 Thomas Monjalon
2020-10-29  3:45 ` 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=62225691.5773307.1603943129372.JavaMail.zimbra@redhat.com \
    --to=pezhang@redhat.com \
    --cc=chayang@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hewang@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.