From: Asaf Penso <asafp@mellanox.com>
To: web@dpdk.org
Cc: olgas@mellanox.com
Subject: [dpdk-web] [PATCH] update Mellanox roadmap for 19.08
Date: Tue, 25 Jun 2019 10:52:10 +0000 [thread overview]
Message-ID: <1561459930-376710-1-git-send-email-asafp@mellanox.com> (raw)
Mellanox roadmap is announced in dpdk mailing list:
https://mails.dpdk.org/archives/dev/2019-June/135099.html
Signed-off-by: Asaf Penso <asafp@mellanox.com>
---
content/roadmap/_index.md | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 1cee44d..1fd0a0e 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -13,8 +13,12 @@ This list is obviously neither complete nor guaranteed.
- new device specification (devargs) syntax
- documentation for device management
-- TCP SEQ and ACK offload with rte_flow API and mlx5 implementation
-- ICMP ping offload with rte_flow API and mlx5 implementation
+- TCP SEQ, TCP ACK and GRE key matching with rte_flow API and mlx5 implementation
+- setting metadata in RX, with rte_flow API and mlx5 implementation, and receiving it as part of mbuf
+- mlx5 offload ICMP ping, IP-in-IP inner RSS, TCP flags matching, LRO and hairpin
+- better mlx5 rte_flow_query rate and latency
+- better mlx5 out of the box TX performance
+- robustness additions in mlx5 data-path error handling and recovery
- initial support for Huawei Intelligent PCIe NIC
### Version 19.11 (2019 September) {#1911}
--
1.8.3.1
next reply other threads:[~2019-06-25 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 10:52 Asaf Penso [this message]
2019-06-25 13:59 ` 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=1561459930-376710-1-git-send-email-asafp@mellanox.com \
--to=asafp@mellanox.com \
--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).