From: James Poole <james.g.poole@intel.com>
To: web@dpdk.org
Cc: James Poole <james.g.poole@intel.com>
Subject: [dpdk-web] [PATCH] roadmap: update to 16.11 roadmap items
Date: Fri, 8 Jul 2016 08:27:44 +0100 [thread overview]
Message-ID: <1467962864-23321-1-git-send-email-james.g.poole@intel.com> (raw)
Signed-off-by: <james.g.poole@intel.com>
---
dev/roadmap.html | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/dev/roadmap.html b/dev/roadmap.html
index 7230b21..eeea712 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -72,10 +72,14 @@
</ul>
<h3 id="1611">Version 16.11 (2016 November)</h3>
<ul>
- <li>Rx Filtering Rework
- <li>QEMU Vhost backend Reconnect
- <li>Delay Packet Copy in Vhost-user
- <li>Fix library and symbol Namespace
+ <li>Cryptodev Support for Hardware Acceleration (via Intel(r) QuickAssist Technology) for Additional Algorithms
+ <li>Cryptodev Support for Software Acceleration for Additional Algorithms
+ <li>Cryptodev Performance Optimisation
+ <li>IPsec Sample App Enhancements
+ <li>Generic Flow Director/Filtering/Classification API
+ <li>Cuckoo Hash Enhancements
+ <li>Add vHost PMD xStats
+ <li>Delay Packet Copy in vHost-User Dequeue
</ul>
<h3 id="cycle">Cycle model</h3>
<p>A typical release should be done after 3 months (was 4 months during 2015).
--
2.5.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.
next reply other threads:[~2016-07-08 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 7:27 James Poole [this message]
2016-07-11 20:49 ` Thomas Monjalon
2016-07-13 11:03 ` Mcnamara, John
2016-07-13 11:55 ` 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=1467962864-23321-1-git-send-email-james.g.poole@intel.com \
--to=james.g.poole@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).