From: "Butler, Siobhan A" <siobhan.a.butler@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Looking forward to DPDK 2.1
Date: Wed, 25 Feb 2015 13:39:58 +0000 [thread overview]
Message-ID: <0C5AFCA4B3408848ADF2A3073F7D8CC86D51353E@IRSMSX109.ger.corp.intel.com> (raw)
Hi all,
The progress on DPDK 2.0 has been really positive and thanks to everyone for contributing and helping to grow our community. We now look onwards to DPDK 2.1 planning which is due to release at the end of July, and we'd like to inform the community of the features that we hope to submit to that release. The current list of features, along with brief descriptions, is included below.
This list is provisional and will naturally change over the lifecycle of the release, and should be taken as guidance on what we hope to submit, not a commitment.
Our aim in providing this information now is to solicit input from the community. We'd like to make sure we avoid duplication or conflicts with work that others are planning, so please feel free to let the community know of any plans that you have for contributions to DPDK in this timeframe. This will allow us to build a complete picture and ensure we avoid duplication of effort. We have seen great community collaboration in DPDK 2.0 and hope that this will increase in 2.1.
I'm sure people will have questions, and will be looking for more information on these features. Further details will be provided by the individual developers over the next few months. We aim to provide early outlines of the features so that we can obtain community feedback as soon as possible. In addition, community calls can be arranged to discuss features as required.
2.1 (Q2 2015) DPDK Features:
* Cuckoo hash - Provide a new hash library based on the cuckoo hashing scheme (see http://www.cs.cmu.edu/~dongz/papers/cuckooswitch.pdf), which shall guarantee worst-case constant lookup time with a better memory utilization, compared to the current implementation.
* IEEE1588 Support for i40e - Support IEEE1588 Standard (PTP) for i40e Ethernet Controller
* Continued development of PCI Hot Plug - Add support for PCI Hotplug Framework in librte_pmd drivers (librte_pmd_ixgbe, librte_pmd_bond, librte_pmd_e1000, librte_pmd_i40e, librte_pmd_virtio, librte_pmd_vmxnet3)
* Packet Framework Enhancements - Enhancements to Packet Framework Port and Table Libraries, as well as IP Pipeline Application, to include additional statistics, better pipeline encapsulation and CLI simplification.
* i40e DCB (ETS only) - Support DCB Enhanced Transmission Selection algorithm with i40e Ethernet controller.
* i40e Mirroring Rule - Add support for port mirroring using i40e Ethernet Controller.
* Additional FM10K Features - Add support for additional usage models for FM10K including: promiscuous mode, mac vlan filter, statistics, vlan offload (strip, insertion, dual), flow control, Tx offload (checksum).
* Dynamic Configuration of RSS on Bonded Slave devices - Support dynamic queues assignment for RX packets. Implementation for a bonding device will require multiple RX queues support on a bonding slave and its dynamic
reconfiguration.
* VXLAN Offload Sample Application - Provide a sample application to demonstrate the usage of VXLAN overlay encapsulation protocol in DPDK.
* Dynamic Memory Management - Add DPDK API's (Rte_free_unused_pages, rte_attach_pages, rte_detach_pages, rte_lazy_allocation) for Dynamic Memory Management for NFV use cases.
Thanks,
Siobhan Butler
<siobhan.a.butler@intel.com>
next reply other threads:[~2015-02-25 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 13:39 Butler, Siobhan A [this message]
2015-02-25 14:52 ` 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=0C5AFCA4B3408848ADF2A3073F7D8CC86D51353E@IRSMSX109.ger.corp.intel.com \
--to=siobhan.a.butler@intel.com \
--cc=dev@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).