From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: harry.van.haaren@intel.com
Cc: web@dpdk.org
Subject: [dpdk-web] [PATCH v2] roadmap for 16.07
Date: Mon, 11 Apr 2016 22:05:54 +0200 [thread overview]
Message-ID: <1460405154-9269-1-git-send-email-thomas.monjalon@6wind.com> (raw)
In-Reply-To: <1460035816-22179-1-git-send-email-harry.van.haaren@intel.com>
From: Harry van Haaren <harry.van.haaren@intel.com>
Add roadmap items for 16.07, remove 16.04 from schedule.
Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
dev/roadmap.html | 67 +++++++++++++++++++++++++++++---------------------------
1 file changed, 35 insertions(+), 32 deletions(-)
v2:
- add more 16.07 topics from mailing list patches
- add some 16.11 topics from discussions
diff --git a/dev/roadmap.html b/dev/roadmap.html
index 6b83e17..b479967 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -40,33 +40,42 @@
<h2>Development roadmap</h2>
<p>Major known features and milestones may be noted here.
This list is obviously neither complete nor guaranteed.
- <h3 id="1604">Version 16.04 (2016 April)</h3>
+ <h3 id="1607">Version 16.07 (2016 July)</h3>
<ul>
- <li>cgroup resource awareness
- <li>hugetlbfs mount point size
- <li>external mempool manager
- <li>Intel resource director technology
- <li>improve live migration
- <li>tcpdump support
- <li>speed capability
- <li>generic tunneling
- <li>Hyper-V driver
- <li>ixgbe base update
- <li>i40e flow director extension
- <li>i40e VEB switching and floating VEB
- <li>i40e IPGRE
- <li>i40e VF MAC address
- <li>i40e PCIe extended tag rework
- <li>fm10k Rx interrupt
- <li>fm10k FTAG based forwarding
- <li>virtio 1.0
- <li>virtio for containers
- <li>vhost TSO
- <li>bonding mode 4 external state machine
- <li>more LPM hops
- <li>SNOW 3G cipher
- <li>IPsec example
- <li>packet framework enhancements for edge router
+ <li>Dynamic Mempool Cache Allocation
+ <li>External Mempool Cache
+ <li>External Mempool Manager
+ <li>Mempool Allocation Rework
+ <li>Packet Capture Framework
+ <li>Automatic Device Binding
+ <li>Hotplug Notification
+ <li>Device Objects Refactoring
+ <li>Flattened Device Tree Access
+ <li>XStats Enhancements
+ <li>bnxt Driver for Broadcom NetXtreme 10/25/50G C-Series
+ <li>qede Driver for QLogic FastLinQ QL4xxxx 25/40G CNA
+ <li>ixgbe/i40e Automatic VF Reset from PF
+ <li>i40e Network Service Header
+ <li>i40e Floating VEB
+ <li>Xen Netfront Driver
+ <li>Vhost/Virtio Performance Loopback Utility
+ <li>Vhost API Refactoring
+ <li>Virtio Rx/Tx Split
+ <li>Virtio Descriptor Index Optimization
+ <li>Virtio in Containers
+ <li>Live Migration for SR-IOV
+ <li>Software implementation of KASUMI Crypto
+ <li>Bit-Level Cryptodev for SNOW 3G
+ <li>IPv6 and Transport Mode in IPsec Sample App
+ <li>IP Pipeline Enhancements
+ <li>Keep-Alive Enhancements
+ </ul>
+ <h3 id="1611">Version 16.11 (2016 November)</h3>
+ <ul>
+ <li>Rx Filtering Rework
+ <li>QEMU Vhost backend Reconnect
+ <li>Delay Packet Copy in Vhost-user
+ <li>Fix library and symbol Namespace
</ul>
<h3 id="cycle">Cycle model</h3>
<p>A typical release should be done after 3 months (was 4 months during 2015).
@@ -82,12 +91,6 @@
<p>The last period is 1 month long and is dedicated to bug fixing.
<h3 id="dates">Scheduling</h3>
<p>The release cycles are progressively shorten during 2016.
- <p>Release 16.04
- <ul>
- <li>Proposal deadline: January 31
- <li>Integration deadline: March 10
- <li>Release: April 7
- </ul>
<p>Release 16.07
<ul>
<li>Proposal deadline: May 8
--
2.7.0
next prev parent reply other threads:[~2016-04-11 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 13:30 [dpdk-web] [PATCH] roadmap: update items to 16.07 Harry van Haaren
2016-04-11 20:05 ` Thomas Monjalon [this message]
2016-04-11 20:10 ` [dpdk-web] [PATCH v2] roadmap for 16.07 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=1460405154-9269-1-git-send-email-thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=harry.van.haaren@intel.com \
--cc=web@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).