From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: david.marchand@redhat.com, asafp@nvidia.com, galco@nvidia.com,
rasland@mellanox.com
Subject: [dpdk-web] [PATCH] update Nvidia roadmap for 20.11
Date: Thu, 24 Sep 2020 01:23:42 +0200 [thread overview]
Message-ID: <20200923232342.1831875-1-thomas@monjalon.net> (raw)
Was announced in the dpdk-dev mailing list:
http://mails.dpdk.org/archives/dev/2020-August/178501.html
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/roadmap/_index.md | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index d486da1..712dae3 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -23,8 +23,16 @@ This list is obviously neither complete nor guaranteed.
- Tx QoS marking API
- flow action object API
- flow sampling and mirroring API
+- flow matching on IPv4/v6 frag/non-frag packets
+- flow matching on Geneve extension header
+- tunnel offload API
+- hairpin between different ports
+- Rx buffer split to multiple destinations
<!-- Network drivers -->
- performance optimizations in mlx drivers for Arm platforms
+- mlx5 Rx buffer split
+- mlx5 flow sampling/mirroring and extended matching
+- mlx5 thread-safe flow rules management and improved performance
- octeontx2 packet mirroring
- octeontx2 rte_tm enhancement
- qede SR-IOV PF
@@ -36,6 +44,8 @@ This list is obviously neither complete nor guaranteed.
- performance test for IP reassembly
- runtime config for burst stats and CPU cycle stats in testpmd
<!-- Crypto -->
+<!-- Compress -->
+- mlx5 compressdev
<!-- Others -->
- regex driver based on libpcre
- Dynamic Load Balancer event driver
--
2.28.0
next reply other threads:[~2020-09-23 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 23:23 Thomas Monjalon [this message]
2020-09-25 8:25 ` Thomas Monjalon
2020-10-05 13:50 Shiri Kuzin
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=20200923232342.1831875-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=asafp@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=galco@nvidia.com \
--cc=rasland@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).