DPDK website maintenance
 help / color / mirror / Atom feed
From: Kevin Laatz <kevin.laatz@intel.com>
To: web@dpdk.org
Cc: ferruh.yigit@intel.com, john.mcnamara@intel.com,
	Kevin Laatz <kevin.laatz@intel.com>
Subject: [dpdk-web] [PATCH v2] update 18.08 roadmap
Date: Tue, 12 Jun 2018 14:58:41 +0100	[thread overview]
Message-ID: <20180612135841.31308-1-kevin.laatz@intel.com> (raw)
In-Reply-To: <20180606150142.3805-1-kevin.laatz@intel.com>

Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>

---
V2:
- Undo removal of features that have been postponed
---
 dev/roadmap.html | 38 ++++++++++++++++----------------------
 1 file changed, 16 insertions(+), 22 deletions(-)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index aabdbf4..8efabd4 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -41,39 +41,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="1805">Version 18.05 (2018 May)</h3>
+	<h3 id="1808">Version 18.08 (2018 August)</h3>
 	<ul>
-		<li>memory subsystem rework
-		<li>uevent support for hotplug
 		<li>new device specification (devargs) syntax
-		<li>secondary process support in virtual devices
-		<li>ethdev API for recommended descriptor ring sizes
-		<li>ethdev API to manage tunnel endpoints
-		<li>ethdev Rx/Tx offloads for various tunnels
-		<li>ethdev switch offloads
-		<li>ethdev port representor
-		<li>i40e PPPoE/PPPoL2Tv2
-		<li>mlx5 striding RQ (multi packets buffer)
-		<li>mlx5 tunnels offloads extended
-		<li>vhost interrupt mode
-		<li>selective datapath in vhost-user library
-		<li>new Intel driver (IFC VF) for accelerated virtio
-		<li>virtio-user for virtio-crypto
 		<li>tap TSO
-		<li>bonding support of flow API
-		<li>new API for hardware and software compression/decompression
 		<li>eventdev ordered and atomic queues for DPAA2
-		<li>eventdev crypto adapter
-		<li>eventdev timer adapter
-		<li>IP pipeline enhancements
 		<li>libedit integration
+		<li>power management: turbo core thread pinning
+		<li>power management: traffic pattern aware power control
+		<li>power management: 100% busy traffic polling
+		<li>failure handler for PCIE hardware hotplug
+		<li>virtio IN_ORDER support
+		<li>allow setup/reconfiguration/tear down of queues at runtime
+		<li>SoftNIC restructuring
+		<li>SoftNIC support for NAT
+		<li>virtual device hotplug
+		<li>Intel(r) QuickAssist Technology Compression PMD
+		<li>vhost-user extension to improve vDPA
+		<li>unified packet fragmentation
+		<li>3DES support in AESNI_MB PMD
+		<li>ISAL Compression PMD enhancements
+		<li>complete Intel PMD support for new descriptor status apis
 	</ul>
 	<h3 id="future">Nice to have - Future</h3>
 	<ul>
 		<li>multi-process rework
 		<li>automatic UIO/VFIO binding
 		<li>infiniband driver class (ibdev)
-		<li>BPF support
 		<li>default configuration from files
 		<li>generic white/blacklisting
 	</ul>
-- 
2.9.5

  parent reply	other threads:[~2018-06-12 13:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 15:01 [dpdk-web] [PATCH] " Kevin Laatz
2018-06-06 15:03 ` Mcnamara, John
2018-06-08 19:27 ` Mcnamara, John
2018-06-12 13:58 ` Kevin Laatz [this message]
2018-06-14  9:01   ` [dpdk-web] [PATCH v2] " Mcnamara, John
2018-06-14 17:17   ` Thomas Monjalon
2018-06-15 10:05   ` [dpdk-web] [PATCH v3] " Kevin Laatz
2018-06-15 10:44     ` 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=20180612135841.31308-1-kevin.laatz@intel.com \
    --to=kevin.laatz@intel.com \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@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).