From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: asafp@nvidia.com
Subject: [dpdk-web] [PATCH 1/1] update Nvidia roadmap for 21.02
Date: Mon, 4 Jan 2021 22:50:43 +0100 [thread overview]
Message-ID: <20210104215043.1557677-1-thomas@monjalon.net> (raw)
Was announced in the dpdk-dev mailing list with more details:
http://mails.dpdk.org/archives/dev/2020-December/194848.html
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/roadmap/_index.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 43fac0d..7dbe4eb 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -16,6 +16,9 @@ This list is obviously neither complete nor guaranteed.
- x86 power management enhancements using UMWAIT and TPAUSE instructions
<!-- Networking -->
- Tx QoS marking API
+- flow data field copy action
+- matching on VXLAN and Geneve extended options
+- device identifier syntax for SF representor
- AVF software back-end driver with device emulation libraries
<!-- Network drivers -->
- bnxt support for BCM58818/Stingray2 device
@@ -25,6 +28,9 @@ This list is obviously neither complete nor guaranteed.
- i40e on Windows
- iavf eCPRI flow offloading
- ice DCF double VLAN offloading
+- mlx5 on Windows
+- mlx5 flow data copy and extended handling of tunnel options
+- mlx5 SF (Scalable Function) representor
- mvpp2 enhancement
- octeon PCIe endpoint driver for smartNIC
- octeontx2 mirroring
@@ -38,6 +44,7 @@ This list is obviously neither complete nor guaranteed.
- IF proxy
- performance test for IP reassembly
- runtime config for burst stats and CPU cycle stats in testpmd
+- multi-threaded rule insertion in flow-perf application
<!-- Crypto -->
- IPv6 in lookaside IPsec example
- anti-replay in inline IPsec example
--
2.29.2
reply other threads:[~2021-01-04 21:50 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=20210104215043.1557677-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=asafp@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).