DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 20.11-rc1
Date: Tue, 20 Oct 2020 18:50:13 +0200	[thread overview]
Message-ID: <1695913.Ws3t40NQoN@thomas> (raw)

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-20 16:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 16:50 Thomas Monjalon [this message]
2020-10-29  3:45 ` Pei Zhang

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=1695913.Ws3t40NQoN@thomas \
    --to=thomas@monjalon.net \
    --cc=announce@dpdk.org \
    /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).