From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 19.05-rc1
Date: Sat, 06 Apr 2019 00:55:32 +0200 [thread overview]
Message-ID: <6245177.T97mKPeXMT@xps> (raw)
A new DPDK release candidate is ready for testing:
https://git.dpdk.org/dpdk/tag/?id=v19.05-rc1
After one big and one short cycle releases, this one looks normal,
delivering -rc1, almost on time, with 678 patches.
The release notes so far:
http://doc.dpdk.org/guides/rel_notes/release_19_05.html
Please think about updating the release notes when you add a feature.
Highlights of 19.05-rc1, grouped by category:
General:
- helloworld on Windows
- C11 memory ordering in spinlock, rwlock and new ticketlock
- lock-free extendable bucket in hash library
- stack library and lock-free stack mempool handler
- DMA mapping for external memory
Networking:
- min/max MTU info
- iterators for multi-ports device
- AF_XDP PMD
- ice: vector instructions
- ice: package download
- i40e: VXLAN-GPE
- ixgbe: promiscuous mode on VF
- ixgbe: loopback for X540/X550
- mlx5: direct rule
- mlx4: secondary process
- failsafe: secondary process
Cryptography:
- more algorithms in IPsec library
- qat asymmetric crypto
Applications:
- live testpmd statistics
- optimized testpmd macswap mode for Arm
- optimized testpmd txonly mode
- multiple flows with testpmd txonly mode
Some features are expected in 19.05-rc2:
- RCU library
- timer management in multi-process
- memif PMD
- nfb PMD
- ipn3ke PMD
We have one month to complete this release cycle.
19.05-rc2 is expected on 10th of April.
Thank you everyone
PS: some extra informations below
About the previous release 19.02.0, it has been decided to have
no maintenance release 19.02.1 because of a lack of interest.
Only one week remaining to propose a talk for China Summit:
https://www.dpdk.org/event/dpdk-china-june-24th-2019
next reply other threads:[~2019-04-05 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 22:55 Thomas Monjalon [this message]
2019-04-07 9:10 ` Thomas Monjalon
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=6245177.T97mKPeXMT@xps \
--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).