DPDK announcements
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 20.08-rc1
Date: Mon, 13 Jul 2020 02:58:30 +0200	[thread overview]
Message-ID: <2553672.smuk0Yhj5f@thomas> (raw)

A new DPDK release candidate is ready for testing:

There are 778 new patches in this snapshot.

Release notes:

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

                 reply	other threads:[~2020-07-13  0:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2553672.smuk0Yhj5f@thomas \
    --to=thomas@monjalon.net \
    --cc=announce@dpdk.org \


* 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).