DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: jerinj@marvell.com
Subject: [dpdk-web] [PATCH] update Marvell roadmap for 19.11
Date: Thu, 12 Sep 2019 17:53:36 +0200	[thread overview]
Message-ID: <20190912155336.3768-1-thomas@monjalon.net> (raw)

The full Marvell roadmap is announced in the dpdk-dev mailing list:
http://mails.dpdk.org/archives/dev/2019-August/140844.html

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 content/roadmap/_index.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index b6b1fb0..94da33a 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -11,6 +11,9 @@ This list is obviously neither complete nor guaranteed.
 
 ### Version 19.11 (2019 November) {#1911}
 
+- configurability of Rx offloads
+- rte_flow patterns for NSH, IGMP, AH
+- rte_flow actions for mirroring and multicast
 - Rx metadata in mbuf, with rte_flow API and mlx5 implementation
 - hairpin forwarding offload, with mlx5 implementation
 - VF configuration from host via representor port id
@@ -23,7 +26,16 @@ This list is obviously neither complete nor guaranteed.
 - optimized algorithm for resizeable hash table
 - lock-free stack mempool handler
 - lock-free l3fwd algorithms
+- eventdev examples in l2fwd-event, l3fwd and ipsec-secgw
+- Nitrox cryptodev
+- OCTEON TX asymmetric crypto
+- OCTEON TX2 cryptodev
+- OCTEON TX2 inline IPsec using rte_security
+- regexdev
 - template based ring API
+- eBPF arm64 JIT
+- KNI IOVA as VA
+- UBSan in build
 
 ### Nice to have - Future {#future}
 ----
-- 
2.23.0


             reply	other threads:[~2019-09-12 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12 15:53 Thomas Monjalon [this message]
2019-09-12 16:27 Jerin Jacob Kollanukkaran
2019-09-12 16:41 ` 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=20190912155336.3768-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=jerinj@marvell.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).