From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 17.05-rc1
Date: Fri, 07 Apr 2017 00:28:07 +0200 [thread overview]
Message-ID: <5943367.i4t7rzMCMR@xps13> (raw)
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v17.05-rc1
It is the first release candidate for DPDK 17.05,
which is going to be the biggest release ever.
There is already 782 patches so it is probably
big enough for a release candidate.
However it is not feature complete yet.
The major changes expected in rc2 are:
- NXP DPAA2 drivers
- Atomic Rules Arkville driver
- PCI and VDEV bus rework
The priority focus is on moving to the new bus model.
You can read the release notes in progress:
http://dpdk.org/doc/guides/rel_notes/release_17_05.html
Some highlights:
- mbuf rework
- event driven programming model
- software eventdev driver
- Cavium OCTEON TX eventdev driver
- Cavium LiquidIO driver
- Wind River AVP driver
- DOCSIS BPI+ crypto
There are a lot of patches pending in patchwork.
They are waiting for a review or a reply.
Please check how you can help making progress on these patches.
Thank you everyone
PS: DPDK is a Linux Foundation Project now :)
reply other threads:[~2017-04-06 22:28 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=5943367.i4t7rzMCMR@xps13 \
--to=thomas.monjalon@6wind.com \
--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).