DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH 1/2] start 2.3 roadmap
Date: Sat, 19 Dec 2015 00:43:40 +0100	[thread overview]
Message-ID: <1450482221-6404-1-git-send-email-thomas.monjalon@6wind.com> (raw)

Add roadmap inputs from Intel
http://dpdk.org/ml/archives/dev/2015-November/029079.html
---
 dev/roadmap.html | 65 +++++++++++++++++---------------------------------------
 1 file changed, 20 insertions(+), 45 deletions(-)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index 0594eee..5c73d85 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -40,58 +40,33 @@
 	<h2>Development roadmap</h2>
 	<p>Major known features and milestones may be noted here.
 	This list is obviously neither complete nor guaranteed.
-	<h3 id="22">Version 2.2 (end of November 2015)</h3>
+	<h3 id="23">Version 2.3 (end of March 2016)</h3>
 	<ul>
-		<li>queue information
+		<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>statistics rework
-		<li>keep-alive
-		<li>merge physical and virtual devices handling
-		<li>OSv support
+		<li>generic tunneling
 		<li>Hyper-V driver
-		<li>Xen driver
-		<li>szedata2 driver
-		<li>mlx5 driver
-		<li>uio MSI-X
-		<li>e1000 Rx interrupt
-		<li>igb TSO
 		<li>ixgbe base update
-		<li>ixgbe VF TSO
-		<li>ixgbe X550 VF RSS
-		<li>ixgbe X550 flow director for VXLAN/NVGRE
-		<li>ixgbe X550 DCB
-		<li>ixgbe X550 IEEE1588
-		<li>i40e base update
-		<li>i40e Rx interrupt
-		<li>i40e DCB
-		<li>i40e filtering more flexible
-		<li>i40e GRE 32-bit key
-		<li>fm10k base update
-		<li>fm10k vector driver
+		<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 TSO
-		<li>fm10k IEEE1588
-		<li>af_packet hotplug
-		<li>vmxnet3 hotplug
-		<li>xenvirt hotplug
-		<li>virtio TSO
-		<li>vhost multiqueue
-		<li>vhost optimization
-		<li>bonding dynamic RSS
+		<li>fm10k FTAG based forwarding
+		<li>virtio 1.0
+		<li>virtio for containers
+		<li>vhost TSO
 		<li>bonding mode 4 external state machine
-		<li>cryptodev API
-		<li>Quick Assist driver
-		<li>AES-NI multi-buffer driver
 		<li>more LPM hops
-		<li>packet framework enhanced for edge router
-		<li>lightweight thread example
-		<li>IEEE1588 example
-		<li>ethtool example
-	</ul>
-	<h3 id="23">Version 2.3 (end of March 2016)</h3>
-	<ul>
-		<li>automatic port binding
-		<li>hardware support listing app
+		<li>SNOW 3G cipher
+		<li>IPsec example
+		<li>packet framework enhancements for edge router
 	</ul>
 	<p>The 3 major release cycles per annum system is designed to allow DPDK
 	to keep evolving at a rapid pace while giving enough opportunity
-- 
2.5.2

             reply	other threads:[~2015-12-18 23:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 23:43 Thomas Monjalon [this message]
2015-12-18 23:50 ` [dpdk-web] [PATCH 2/2] update release scheduling for 2016 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=1450482221-6404-1-git-send-email-thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.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).