From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: mkashani@nvidia.com
Subject: [PATCH] update NVIDIA roadmap
Date: Wed, 22 Jan 2025 12:11:36 +0100 [thread overview]
Message-ID: <20250122111136.1725397-1-thomas@monjalon.net> (raw)
Was announced in the dpdk-dev mailing list:
https://mails.dpdk.org/archives/dev/2024-December/311009.html
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/roadmap/_index.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index abbb9e3..94b722a 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -22,13 +22,19 @@ This list is obviously neither complete nor guaranteed.
<!-- General -->
- replace VLAs (required by MSVC)
- replace packing attributes (required by MSVC)
+- improve PCI address comparisons
<!-- DMA -->
<!-- Networking -->
+- enable/disable counters
<!-- Network drivers -->
- ena dynamic HRSS size
- ena asynchronous reset request from device
- enetc NXP driver version 4
- eqos NXP driver
+- mlx5 probing optimization
+- mlx5 FDB flows optimization
+- mlx5 eCPRI matching with template API
+- mlx5 ipool debuggability
- xsc Yunsilicon driver
<!-- Virtualisation -->
<!-- Network apps -->
--
2.47.1
reply other threads:[~2025-01-22 11:11 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=20250122111136.1725397-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=mkashani@nvidia.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).