DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: david.marchand@redhat.com, honnappa.nagarahalli@arm.com,
	niklas.soderlund@corigine.com, liudongdong3@huawei.com,
	jerinj@marvell.com, lmargalit@nvidia.com,
	mb@smartsharesystems.com
Subject: [PATCH 6/7] update NVIDIA roadmap for 22.11
Date: Sun, 27 Nov 2022 21:12:44 +0100	[thread overview]
Message-ID: <20221127201245.884619-7-thomas@monjalon.net> (raw)
In-Reply-To: <20221127201245.884619-1-thomas@monjalon.net>

Was announced in the dpdk-dev mailing list:
https://mails.dpdk.org/archives/dev/2022-September/250487.html

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

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 17584da..05d8615 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -27,8 +27,15 @@ This list is obviously neither complete nor guaranteed.
 - protocol-based header split
 - ethdev congestion management
 - protocol parameter in color table update
+- ethdev hairpin memory capabilities
 - ethdev flow rules pre-configuration flags
+- ethdev port type hint when creating transfer table
+- ethdev flow action to route packet to kernel
+- ethdev async flow connection tracking configuration
+- ethdev indirect action async query
+- ethdev indirect age action update
 - ethdev queue-based ageing event info
+- ethdev flow modify action with GTP PSC QFI
 - ethdev event subtypes for IPsec SA expiry
 - ethdev error report/recovery event
 - ethdev trace points
@@ -39,6 +46,8 @@ This list is obviously neither complete nor guaranteed.
 <!-- Network drivers -->
 - bonding Tx prepare
 - memif performance optimization
+- mlx5 flow template and asynchronous queue-based management
+- mlx5 port representor matching
 - nfp flower firmware
 - nfp representor port
 - nfp flow offload
-- 
2.36.1


  parent reply	other threads:[~2022-11-27 20:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 20:12 [PATCH 0/7] 22.11 roadmaps Thomas Monjalon
2022-11-27 20:12 ` [PATCH 1/7] update DTS roadmap for 22.11 Thomas Monjalon
2022-11-27 20:12 ` [PATCH 2/7] update Arm " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 3/7] update Corigine " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 4/7] update Huawei " Thomas Monjalon
2022-11-27 20:12 ` [PATCH 5/7] update Marvell " Thomas Monjalon
2022-11-27 20:12 ` Thomas Monjalon [this message]
2022-11-27 20:12 ` [PATCH 7/7] update SmartShare Systems " Thomas Monjalon
2022-11-27 20:43   ` Morten Brørup
2022-11-27 21:34     ` 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=20221127201245.884619-7-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=liudongdong3@huawei.com \
    --cc=lmargalit@nvidia.com \
    --cc=mb@smartsharesystems.com \
    --cc=niklas.soderlund@corigine.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).