DPDK announcements
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 20.11-rc2
Date: Wed, 04 Nov 2020 23:02:48 +0100	[thread overview]
Message-ID: <2353813.dmDHS9aCqr@thomas> (raw)

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

There are 628 new patches in this snapshot.
The good news is that -rc2 is smaller than -rc1 ;)

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

Highlights of 20.11-rc2:
	- ring zero copy
	- mbuf dynamic fields space increased from 16 to 36 bytes
	- removed mbuf userdata/seqn/timestamp fields
	- removed legacy ethdev filtering
	- RCU in hash library
	- AVX512 lookup in FIB
	- Intel DLB/DLB2 drivers
	- Wangxun txgbe driver

The -rc3 should include only some bug fixes, cleanups, doc and tooling.
We have until the end of next week to complete this milestone.
Then at least one more week (allowing -rc4) should be needed
before the release.

Please test, report and fix issues on bugs.dpdk.org.
As a community, we must close as many bugs as possible for -rc3.

We are getting closer to a well deserved rest.
Thank you everyone



                 reply	other threads:[~2020-11-04 22:02 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:
  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=2353813.dmDHS9aCqr@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).