From: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
To: web@dpdk.org
Cc: tim.odriscoll@intel.com, Herakliusz Lipiec <herakliusz.lipiec@intel.com>
Subject: [dpdk-web] [PATCH] update roadmap
Date: Thu, 11 May 2017 16:14:28 +0100 [thread overview]
Message-ID: <1494515668-8898-1-git-send-email-herakliusz.lipiec@intel.com> (raw)
Signed-off-by: Herakliusz Lipiec <herakliusz.lipiec@intel.com>
---
dev/roadmap.html | 30 ++++++------------------------
1 file changed, 6 insertions(+), 24 deletions(-)
diff --git a/dev/roadmap.html b/dev/roadmap.html
index 428ed84..4569663 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -41,24 +41,6 @@
<h2>Development roadmap</h2>
<p>Major known features and milestones may be noted here.
This list is obviously neither complete nor guaranteed.
- <h3 id="1705">Version 17.05 (2017 May)</h3>
- <ul>
- <li>Event Driven Model
- <li>Rearrange mbuf structure for performance and add timestamp
- <li>Ethernet 32-bit CRC
- <li>Extended Statistics for latency and bit rate
- <li>Free Tx mbuf on demand
- <li>Atomic Rules Arkville Driver
- <li>NXP FSLMC Bus and DPAA2 Driver
- <li>MTU for virtio
- <li>Interrupt Mode for virtio-user
- <li>New device types in vhost-user
- <li>Add flow API and virtual functions support in the Solarflare net driver
- <li>Tunnel and MPLS filters for i40e
- <li>Automated VF processing of PF Reset for i40e
- <li>Consistent PMD Batching behaviour
- <li>Cryptodev DOCSIS BPI+
- </ul>
<h3 id="1708">Version 17.08 (2017 August)</h3>
<ul>
<li>Hotplug Notification
@@ -70,6 +52,12 @@
<li>NXP DPAA2 Eventdev Driver
<li>NXP DPAA1 Bus, Mempool and PMD
<li>ARM Architecture support in Atomic Rules Arkville Driver
+ <li>Generic QoS API
+ <li>Generic Receive Offload
+ <li>Generic Flow Enhancements
+ <li>Packet Type Recognition in IXGBE Vector PMD
+ <li>VF Restore After PF Reset
+ <li>Cryptodev Multi-Core SW Scheduler
</ul>
<h3 id="cycle">Cycle model</h3>
<p>A typical release should be done after 3 months.
@@ -84,12 +72,6 @@
<p>At the end of the merge window, the first release candidate is out.
<p>The last period is 1 month long and is dedicated to bug fixing.
<h3 id="dates">Scheduling</h3>
- <p>17.05
- <ul>
- <li>Proposal deadline: March 3
- <li>Integration deadline: March 30
- <li>Release: May 2
- </ul>
<p>17.08
<ul>
<li>Proposal deadline: May 28
--
2.7.4
next reply other threads:[~2017-05-11 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 15:14 Herakliusz Lipiec [this message]
2017-05-11 15:02 ` Mcnamara, John
2017-05-17 11:17 ` 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=1494515668-8898-1-git-send-email-herakliusz.lipiec@intel.com \
--to=herakliusz.lipiec@intel.com \
--cc=tim.odriscoll@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).