DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: mkashani@nvidia.com, galco@nvidia.com, asafp@nvidia.com
Subject: [PATCH] update NVIDIA roadmap for 23.11
Date: Tue, 15 Aug 2023 17:35:55 +0200	[thread overview]
Message-ID: <20230815153555.522925-1-thomas@monjalon.net> (raw)

Was announced in the dpdk-dev mailing list:

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

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index e0917f7..3a4f2a0 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -22,6 +22,12 @@ This list is obviously neither complete nor guaranteed.
 - dmadev trace points
 <!-- Networking -->
 - buffer recycle (a.k.a direct-rearm of Rx side buffers)
+- ESP packet type
+- flow color-aware mode for meters in shared actions list
+- flow action for NAT64
+- flow group miss action
+- flow item for packet type matching
+- flow template hash
 <!-- Network drivers -->
 - ntnic driver from Napatech
 - rnp driver from Mucse
@@ -29,6 +35,13 @@ This list is obviously neither complete nor guaranteed.
 - cnxk mirroring
 - cnxk flow aging
 - cnxk port representor
+- mlx5 more tags with flow template
+- mlx5 parsing of VXLAN-GPE with NSH
+- mlx5 flow actions for Geneve and IPv6 extension push/remove
+- mlx5 indirect action for quota and raw encap/decap
+- mlx5 transfer traffic to representor
+- mlx5 switch between 2 physical ports
+- mlx5 hairpin up to 4 physical ports and queue counters
 <!-- Virtualisation -->
 - vhost small copy with CPU in DSA-accelerated vhost
 - vhost port mirroring with DMAdev

                 reply	other threads:[~2023-08-15 15:36 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230815153555.522925-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=asafp@nvidia.com \
    --cc=galco@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=web@dpdk.org \


* 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).