DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: olgas@mellanox.com
Subject: [dpdk-web] [PATCH] update Mellanox roadmap for 18.08
Date: Fri, 15 Jun 2018 16:29:18 +0200	[thread overview]
Message-ID: <20180615142918.11272-1-thomas@monjalon.net> (raw)

The roadmap was announced in this email:
	http://dpdk.org/ml/archives/dev/2018-June/104186.html

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 dev/roadmap.html | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index 3fcf698..7ab3004 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -47,6 +47,13 @@
 		<li>power management: turbo core thread pinning
 		<li>power management: traffic pattern aware power control
 		<li>power management: 100% busy traffic polling
+		<li>add MPLS to rte_flow encapsulation API
+		<li>add metadata matching in rte_flow API
+		<li>mlx5: add representors (including for BlueField SmartNIC)
+		<li>mlx5: support rte_flow port and VLAN actions
+		<li>mlx5: support VXLAN and MPLS encapsulations
+		<li>mlx4: support TSO offload for ConnectX-3 Pro
+		<li>mlx: support 32-bit compilation
 		<li>complete support of new descriptor status API for Intel PMDs
 		<li>failure handler for PCIE hardware hotplug
 		<li>virtual device hotplug
@@ -56,6 +63,7 @@
 		<li>vhost: buffer vectors generalization
 		<li>vhost-user extension to improve vDPA
 		<li>tap TSO
+		<li>tap and failsafe support in multi-process
 		<li>SoftNIC restructuring to use Packet Framework
 		<li>SoftNIC support for NAT
 		<li>eventdev ordered and atomic queues for DPAA2
-- 
2.17.1

             reply	other threads:[~2018-06-15 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 14:29 Thomas Monjalon [this message]
2018-06-15 15:00 ` Mcnamara, John
2018-06-18 16:53   ` 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=20180615142918.11272-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=olgas@mellanox.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).