From: James Poole <james.g.poole@intel.com>
To: web@dpdk.org
Cc: john.mcnamara@intel.com, James Poole <james.g.poole@intel.com>
Subject: [dpdk-web] [PATCH v2] roadmap: update to 16.11 roadmap
Date: Mon, 25 Jul 2016 09:00:11 +0100 [thread overview]
Message-ID: <1469433611-27405-1-git-send-email-james.g.poole@intel.com> (raw)
Signed-off-by: James Poole <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..eace697 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>Additional Hardware and Software Crypto Algorithms</li>
+ <li>Cryptodev Performance Optimisation</li>
+ <li>Support for AES-GCM, AES-CTR, config file support to remove hard-coding of SAs/SPs etc.</li>
+ <li>Use forward cipher function to generate IV on CBC mode</li>
+ <li>Generic Rx Filtering API</li>
+ <li>Optimize the Cuckoo Hash lookup stages by using intelligent prefetching for keys and using IA AVX instructions for vector processing of keys</li>
+ <li>vHost PMD xStats</li>
+ <li>Delay Packet Copy in vHost-User Dequeue</li>
</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
next reply other threads:[~2016-07-25 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 8:00 James Poole [this message]
2016-07-26 9:37 ` Mcnamara, John
2016-07-27 14:54 ` Thomas Monjalon
2016-07-29 12:46 ` Mcnamara, John
2016-07-29 13:11 ` 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=1469433611-27405-1-git-send-email-james.g.poole@intel.com \
--to=james.g.poole@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).