From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH 2/2] add 17.11 roadmap from Intel, Mellanox and Netronome
Date: Wed, 30 Aug 2017 23:43:31 +0200 [thread overview]
Message-ID: <20170830214331.8920-2-thomas@monjalon.net> (raw)
In-Reply-To: <20170830214331.8920-1-thomas@monjalon.net>
Roadmaps are announced on the mailing list:
http://dpdk.org/ml/archives/dev/2017-July/071888.html
http://dpdk.org/ml/archives/dev/2017-July/071909.html
http://dpdk.org/ml/archives/dev/2017-July/071918.html
http://dpdk.org/ml/archives/dev/2017-August/073446.html
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
dev/roadmap.html | 27 +++++++++++++++++++++++----
1 file changed, 23 insertions(+), 4 deletions(-)
diff --git a/dev/roadmap.html b/dev/roadmap.html
index 6c9d85b..8ac41f7 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -43,10 +43,29 @@
This list is obviously neither complete nor guaranteed.
<h3 id="1711">Version 17.11 (2017 November)</h3>
<ul>
- <li>Vhost-user IOMMU support
- <li>NXP DPAA1 Bus, Mempool and PMD
- <li>ARM Architecture support in Atomic Rules Arkville Driver
- <li>VF Restore after PF Reset
+ <li>Extend port ID to 2 bytes
+ <li>New Rx/Tx offload API
+ <li>IPsec offload API
+ <li>QoS metering and policing API
+ <li>QoS traffic management software fallback
+ <li>Example application for <a href="/doc/api/rte__tm_8h.html">QoS traffic management</a>
+ <li>Example application for <a href="/doc/api/rte__flow_8h.html">rte_flow API</a>
+ <li>GSO (Generic Segmentation Offload) library
+ <li>Example application for GRO heavyweight mode
+ <li>RSS queue regions API for <a href="/doc/guides/nics/i40e.html">i40e PMD</a>
+ <li>NXP DPAA1 bus, mempool and PMD
+ <li>ARM support in <a href="/doc/guides/nics/ark.html">ark PMD</a>
+ <li>PF support in <a href="/doc/guides/nics/nfp.html">nfp PMD</a>
+ <li>VF restore after PF reset
+ <li>Rework mlx drivers for <a href="https://github.com/linux-rdma/rdma-core/tree/master/libibverbs">upstream ibverbs</a> support
+ <li>Support secondary process, plug out, raw timestamp and flow counter in <a href="/doc/guides/nics/mlx5.html">mlx5 PMD</a>
+ <li>Support secondary process in virtual devices
+ <li>IOMMU support in vhost-user
+ <li><a href="https://en.wikipedia.org/wiki/Data_Encryption_Standard">DES</a> software PMD with AVX512 optimization
+ <li><a href="https://en.wikipedia.org/wiki/CCM_mode">AES CCM</a> in OpenSSL PMD
+ <li>Performance enhancements in <a href="/doc/guides/cryptodevs/qat.html">qat PMD</a>
+ <li>Per-core turbo boost in power management library
+ <li>Power management policy control
</ul>
<h3 id="1802">Version 18.02 (2018 February)</h3>
<ul>
--
2.14.1
next prev parent reply other threads:[~2017-08-30 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 21:43 [dpdk-web] [PATCH 1/2] remove 17.08 from roadmap Thomas Monjalon
2017-08-30 21:43 ` Thomas Monjalon [this message]
2017-09-01 8:09 ` [dpdk-web] [PATCH 2/2] add 17.11 roadmap from Intel, Mellanox and Netronome Maxime Coquelin
2017-09-04 22:21 ` Thomas Monjalon
2017-09-01 8:16 ` [dpdk-web] [PATCH 1/2] remove 17.08 from roadmap Maxime Coquelin
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=20170830214331.8920-2-thomas@monjalon.net \
--to=thomas@monjalon.net \
--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).