From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [PATCH] update NVIDIA roadmap for 23.07
Date: Wed, 17 May 2023 16:54:23 +0200 [thread overview]
Message-ID: <20230517145423.119550-1-thomas@monjalon.net> (raw)
Was announced in the dpdk-dev mailing list:
https://mails.dpdk.org/archives/dev/2023-April/267017.html
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/roadmap/_index.md | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index da77e76..68f1960 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -12,6 +12,7 @@ This list is obviously neither complete nor guaranteed.
### Version 23.07 (2023 July) {#2307}
<!-- General -->
+- memzones configuration at runtime
- non-temporal memory copy
- mempool cache zero-copy get/put bulk
- index-based per core mempool cache
@@ -23,12 +24,23 @@ This list is obviously neither complete nor guaranteed.
- direct-rearm of Rx side buffers
- Tx QoS marking API
- ethdev telemetry RSS, Rx/Tx burst mode info
+- flow item for RoCE
+- flow actions for IPv6 extensions push/remove
+- flow modify action for complex tunneling
+- flow template mirror action
+- flow template actions update
<!-- Network drivers -->
+- mlx5 Tx tracing
+- mlx5 packet size matching
+- mlx5 flow matching of all switch ports in one rule
+- mlx5 kernel routing with flow template
+- mlx5 MPLS modify action
+- mlx5 quota
+- mlx5 multi-packet write on Windows ???
- octeontx2 mirroring
- qede initial support for next generation hardware
- qede flow API support
- spnic driver for Ramaxel devices
-- mlx5 flow matching of all switch ports in one rule
<!-- Virtualisation -->
- vhost small copy with CPU in DSA-accelerated vhost
- vhost port mirroring with DMAdev
@@ -36,6 +48,7 @@ This list is obviously neither complete nor guaranteed.
<!-- Network apps -->
- testpmd attach/detach on primary and secondary
<!-- Crypto -->
+- mlx5 AES-GCM
- qat without dependency on OpenSSL-1.x
<!-- Compress -->
<!-- Event -->
--
2.40.1
reply other threads:[~2023-05-17 14:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230517145423.119550-1-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).