From: Marko Kovacevic <marko.kovacevic@intel.com>
To: web@dpdk.org
Cc: ferruh.yigit@intel.com, john.mcnamara@intel.com,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: [dpdk-web] [PATCH v2] update roadmap for 18.11
Date: Tue, 11 Sep 2018 16:44:47 +0100 [thread overview]
Message-ID: <20180911154447.4325-1-marko.kovacevic@intel.com> (raw)
Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
---
V2: Removed feature that was merged into 18.08
---
content/roadmap/_index.md | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 166bf4a..5451767 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -19,10 +19,20 @@ This list is obviously neither complete nor guaranteed.
- failure handler for PCIE hardware hotplug
- virtual device hotplug
- tap and failsafe support in multi-process
-- SoftNIC support for NAT
- eventdev ordered and atomic queues for DPAA2
- libedit integration
- noisy VNF forward mode in testpmd
+- Add Crypto Support to Packet Framework:
+- AES-CMAC Support in QAT PMD
+- FIPS Test Suite
+- QAT Compression PMD Enhancements
+- Compression Performance Test App
+- vDPA Sample Application
+- Add Classification and Metering Support to SoftNIC
+- Ability to use Externally Allocated Memory
+- Telemetry API
+- IPsec Library
+- Add Extended Table to Hash Library
### Nice to have - Future {#future}
----
--
2.9.5
next reply other threads:[~2018-09-11 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 15:44 Marko Kovacevic [this message]
2018-09-11 16:06 ` Ferruh Yigit
2018-09-11 17:53 ` Thomas Monjalon
2018-09-12 10:59 ` [dpdk-web] [PATCH v3] " Marko Kovacevic
2018-09-12 12:41 ` [dpdk-web] [PATCH v4] update Intel " Thomas Monjalon
2018-09-12 15:10 ` Ferruh Yigit
2018-09-12 16:20 ` Thomas Monjalon
2018-09-12 16:47 ` Ferruh Yigit
2018-10-16 9:18 ` 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=20180911154447.4325-1-marko.kovacevic@intel.com \
--to=marko.kovacevic@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).