DPDK website maintenance
 help / color / mirror / Atom feed
From: Brian Archbold <brian.archbold@intel.com>
To: web@dpdk.org
Cc: Brian Archbold <brian.archbold@intel.com>
Subject: [dpdk-web] [PATCH v1] update roadmap for 18.05
Date: Thu, 22 Feb 2018 07:23:13 +0000	[thread overview]
Message-ID: <20180222072313.4370-1-brian.archbold@intel.com> (raw)

Update the 18.05 roadmap

Signed-off-by: Brian Archbold <brian.archbold@intel.com>
---
 dev/roadmap.html | 35 ++++++++++++++---------------------
 1 file changed, 14 insertions(+), 21 deletions(-)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index a2fea2f..3bb417d 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -41,28 +41,21 @@
 	<h2>Development roadmap</h2>
 	<p>Major known features and milestones may be noted here.
 	This list is obviously neither complete nor guaranteed.
-	<h3 id="1802">Version 18.02 (2018 February)</h3>
+	<h3 id="1802">Version 18.05 (2018 May)</h3>
 	<ul>
-		<li>meson/ninja build system
-		<li>memory management rework
-		<li>hotplug, notifications and device ownership
-		<li>new device specification (devargs) syntax
-		<li>secondary process support in virtual devices
-		<li>ethdev port representor driver
-		<li>adaptive virtual function (AVF) driver
-		<li>ARM support for ark
-		<li>qede tunneling offloads
-		<li>mlx5 IPsec offload
-		<li>security protocol offload support for DPAA
-		<li>virtual address support for DPAA2
-		<li>virtio-crypto driver
-		<li>eventdev driver for DPAA
-		<li>eventdev ordered and atomic queues for DPAA2
-		<li>eventdev optimized packet distribution library (OPDL) driver
-		<li>eventdev crypto adapter
-		<li>base band device class (bbdev)
-		<li>raw device class
-		<li>libedit integration
+		<li>Provide support for a selective datapath in the vhost-user library
+		<li>Add a new Intel device driver (IFC VF) for accelerated virtio data path
+		<li>Add support for interrupt mode to vhost
+		<li>Virtio-User for virtio-crypto
+		<li>Add new ethdev API to query recommended Descriptor Ring sizes
+		<li>Add additional Memory Subsystem improvements
+		<li>IP Pipeline Usability Enhancements
+		<li>Provide a new API to support hardware and software compression/decompression
+		<li>Add a new API to manage tunnel end points
+		<li>Add Port Representor, a virtual PMD with a logical representation of any port
+		<li>Support PPPoE/PPPoL2Tv2 in I40E PMD
+		<li>Update Intel PMDs for Tx/Tx Offload API
+		<li>Add Uevent Support for Hotplug
 	</ul>
 	<h3 id="future">Nice to have - Future</h3>
 	<ul>
-- 
2.9.5

--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.

             reply	other threads:[~2018-02-22 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22  7:23 Brian Archbold [this message]
2018-02-26 12:17 ` Mcnamara, John
2018-02-26 14:17   ` Thomas Monjalon
2018-02-26 15:18     ` Mcnamara, John

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=20180222072313.4370-1-brian.archbold@intel.com \
    --to=brian.archbold@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).