From: Ferruh Yigit <ferruh.yigit@intel.com>
To: web@dpdk.org
Cc: John McNamara <john.mcnamara@intel.com>
Subject: [PATCH v2] update Intel roadmap for 22.03
Date: Fri, 10 Dec 2021 20:10:21 +0000 [thread overview]
Message-ID: <20211210201021.4153238-1-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20211125133445.1631067-1-ferruh.yigit@intel.com>
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
--
Cc: John McNamara <john.mcnamara@intel.com>
v2:
* Rebase
---
content/roadmap/_index.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 069c5c4bb013..6b33234bdb16 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -19,7 +19,10 @@ This list is obviously neither complete nor guaranteed.
- IP reassembly offload
- AVF software back-end driver with device emulation libraries
<!-- Network drivers -->
+- af_xdp secondary process
+- af_xdp with libxdp library
- bonding Tx prepare
+- ice flow director and flow API enhancements
- mlx5 inline IPsec ESP crypto
- octeontx2 mirroring
- qede initial support for next generation hardware
@@ -28,6 +31,8 @@ This list is obviously neither complete nor guaranteed.
- vhost async dequeue for split ring and enable in vhost sample app
<!-- Network apps -->
<!-- Crypto -->
+- qat async crypto
+- qat with OpenSSL3.0 library
<!-- Compress -->
<!-- Event -->
- event vector support in SW Rx eventdev adapter
--
2.33.1
next prev parent reply other threads:[~2021-12-10 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 13:34 [PATCH] " Ferruh Yigit
2021-12-10 20:10 ` Ferruh Yigit [this message]
2021-12-13 11:01 ` [PATCH v2] " 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=20211210201021.4153238-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.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).