From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 2.2.0-rc2
Date: Thu, 26 Nov 2015 01:19:17 +0100 [thread overview]
Message-ID: <3386333.ETM0rfysfL@xps13> (raw)
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v2.2.0-rc2
Changelog (main changes since 2.2.0-rc1)
- enhancements:
* ARM v7
* ARM v8
* option -d works with directories
* keep alive monitoring
* more sched subports
* precision time protocol with Intel devices
* szedata2 100G networking driver
* crypto API (experimental)
* Intel AES-NI multi-buffer crypto driver
* Intel QuickAssist crypto driver
* more in packet framework
- fixes for:
* compilation
* drivers
* unit tests
The release 2.2.0 is planned for mid-December.
It means there are only two weeks remaining to do some code changes.
So only fixes should be accepted with very few exceptions.
The pending patches about the build system and the examples
are still candidates for the RC3.
There are still some compilation issues. Please consider them as the
highest priority in the coming days.
Thank you everyone
reply other threads:[~2015-11-26 0:20 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=3386333.ETM0rfysfL@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).