From: Ferruh Yigit <ferruh.yigit@intel.com>
To: web@dpdk.org
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] [PATCH] update Intel roadmap for 21.02
Date: Mon, 14 Dec 2020 14:16:45 +0000 [thread overview]
Message-ID: <20201214141645.387310-1-ferruh.yigit@intel.com> (raw)
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
content/roadmap/_index.md | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 456690266cfc..1eec863566c2 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -13,13 +13,19 @@ This list is obviously neither complete nor guaranteed.
<!-- General -->
- Arm CRC32 in generic API
+- Power management enhancements using UMWAIT and TPAUSE instructions
<!-- Networking -->
- Tx QoS marking API
+- AVF software back-end driver with device emulation libraries
<!-- Network drivers -->
- bnxt mirroring
- octeontx2 mirroring
- qede flow API support
+- iavf eCPRI flow offloading support
+- ice DCF double VLAN offloading support
+- i40e support on Windows
<!-- Virtualisation -->
+- vhost async data path performance optimizations
<!-- Network apps -->
- IF proxy
- performance test for IP reassembly
@@ -27,11 +33,13 @@ This list is obviously neither complete nor guaranteed.
<!-- Crypto -->
- IPv6 in lookaside IPsec example
- anti-replay in inline IPsec example
+- support enqueue and dequeue callbacks on cryptodev
<!-- Compress -->
- mlx5 compressdev
<!-- Others -->
- regex driver based on libpcre
- UBSan in build
+- Dynamic Load Balancer event driver common code consolidation
### Nice to have - Future {#future}
----
--
2.29.2
next reply other threads:[~2020-12-14 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 14:16 Ferruh Yigit [this message]
2021-01-04 20: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=20201214141645.387310-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--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).