DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] DPDK 2.1.0 released
Date: Mon, 17 Aug 2015 23:53:01 +0200	[thread overview]
Message-ID: <5975366.UDFeoEJ0m1@xps13> (raw)

A new DPDK release can be downloaded here:
	http://dpdk.org/browse/dpdk/tag/?id=v2.1.0

Every 4 months, a new release.
Every 4 months, more changes than before.
Once again, it is the biggest release ever.

Statistics for this release cycle:
	827 patches from 84 authors
	827 files changed, 131457 insertions(+), 25320 deletions(-)

One of the most interesting number of this release is the record of
54 *new* contributors (including authors, reviewers and testers):

Thanks to Alejandro Lucero, Alex Rosenbaum, Alin Rauta, Anbarasan Murugesan, 
Andrew Harvey, Andrey Chilikin, Bruce Liu, David Harton, Ding Zhi, 
Erik Ziegenbalg, Ferruh Yigit, Gaetan Rivet, Gilad Berman, Harish Patil, 
Hyun Yoo, James Davidson, Jan Blunck, Jan Viktorin, Jasvinder Singh, 
Jean Dao, Johan Faltstrom, Joongi Kim, Klaus Degner, Krishna Murthy, 
Kumar Sanghvi, Liang-Min Larry Wang, Li Wei, Luke Gorrie, Maryam Tahhan, 
Miguel Bernal Marin, Nelio Laranjeiro, Nikita Kozlov, Nitzan Weller, Or Ami, 
Peng Sun, Piotr Azarewicz, Rahul Lakkireddy, Raz Amir, Roman Dementiev, 
Sergey Balabanov, Shaopeng He, Shiweixian, Sotiris Salloumis, Tero Aho, 
Thomas Long, Wang Xiao W, Wenfeng Liu, Wenzhuo Lu, Xavier Simonart, 
Yuichi Nakai, Zhe Tao, Zhigang Lu, Zi Hu and Zoltan Kiss.

These new contributors are associated with these domain names:
6wind.com, allegro-packets.com, an.kaist.ac.kr, arraynetworks.com.cn,
brocade.com, chelsio.com, cisco.com, fujitsu.com, coriant.com, ecotelecom.ru,
elyzion.net, ericsson.com, ezchip.com, gmail.com, huawei.com, infradead.org,
intel.com, linaro.org, mellanox.com, netinsight.net, netronome.com,
qlogic.com, qq.com, rehivetech.com and snabb.co.

Changelog (main enhancements since 2.0.0):
	* memory size without hugepage
	* interrupt mode
	* check mbuf private area alignment
	* indirect mbuf cloning
	* packet type
	* memzone freeing
	* IEEE1588 timestamping
	* multicast filtering
	* flow director extension
	* hash key size
	* hotplug in BSD 
	* e1000 hotplug
	* e1000 82583V jumbo
	* igb dump
	* ixgbe base update
	* ixgbe hotplug
	* ixgbe LRO 
	* ixgbe vector offload extension
	* ixgbe dump
	* i40e base update
	* i40e hotplug
	* i40e port mirroring
	* i40e QinQ
	* fm10k hotplug
	* fm10k jumbo
	* fm10k promiscuous
	* fm10k mac vlan filtering
	* fm10k Tx checksum offload
	* mlx4 update
	* bnx2x driver
	* cxgbe driver
	* vmxnet3 vlan filtering
	* virtio hotplug
	* vhost migration
	* pcap jumbo
	* ring PMD hotplug
	* bonding hotplug
	* 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

New features for 2.2 cycle must be submitted before October.
Features properly reviewed and approved before October 23rd will be part of
the December release.

Hope you'll enjoy this summer release from a fast growing community!

                 reply	other threads:[~2015-08-17 21:54 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=5975366.UDFeoEJ0m1@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).