From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 2.1.0-rc1
Date: Mon, 20 Jul 2015 04:21:50 +0200 [thread overview]
Message-ID: <21138242.6OKcuZkzmo@xps13> (raw)
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v2.1.0-rc1
This is the first release candidate for DPDK 2.1.
It means we are entering in the RC testing phase.
Only fixes and cleanups will be accepted.
Changelog (main enhancements since 2.0.0)
* memory size without hugepage
* indirect mbuf cloning
* packet type
* memzone freeing
* IEEE1588 timestamping
* multicast filtering
* flow director extension
* hash key size
* hotplug in BSD
* e1000 hotplug
* igb dump
* ixgbe base update
* ixgbe hotplug
* ixgbe LRO
* ixgbe dump
* i40e base update
* i40e hotplug
* i40e port mirroring
* i40e QinQ
* fm10k hotplug
* fm10k promiscuous
* fm10k mac vlan filtering
* mlx4 update
* cxgbe driver
* vmxnet3 vlan filtering
* virtio hotplug
* vhost migration
* pcap jumbo
* TILE-Gx architecture
* HTM lock elision for x86
* jhash update
* toeplitz hash
* cuckoo hash
* KNI optimization
* KNI multicast
* packet framework enhancements
* cmdline polling mode
* VXLAN example
You are welcome to review pending patches from other developers
in http://dpdk.org/dev/patchwork and send your comments:
http://dpdk.org/dev#review
There were a lot of interesting dicussions during this release cycle which led
to create and improve the guidelines document. The drawback is that several
important design choices were done late. That's why the deadline for feature
acceptance (i.e. rc1) was extended.
The goal is now to make the release 2.1.0 available on August 12, with a new
release candidate each week. Hope the -rc4 will be the last one.
Please test this release candidate with your hardware and your preferred apps.
Thank you everyone for making each version better!
reply other threads:[~2015-07-20 2:23 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=21138242.6OKcuZkzmo@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).