From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Cc: web@dpdk.org, dev@dpdk.org,
Tim O'Driscoll <tim.odriscoll@intel.com>,
John Mcnamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] [PATCH] update Intel roadmap for 20.02
Date: Fri, 13 Dec 2019 11:02:41 +0000 [thread overview]
Message-ID: <20191213110241.74371-1-ferruh.yigit@intel.com> (raw)
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
Roadmap provided by:
Cc: Tim O'Driscoll <tim.odriscoll@intel.com>
Cc: John Mcnamara <john.mcnamara@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 ed727f0..ae43c16 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -21,6 +21,14 @@ This list is obviously neither complete nor guaranteed.
- regexdev
- template based ring API
- UBSan in build
+- Add cryptodev support for chachapoly symmetric algorithm in Intel QAT devices
+- Flow API support for flow director rules based on Intel DDP profiles
+- Update AESNI-MB PMD and AESNI GCM PMDs to use the latest version of the IPsec multi-buffer library
+- Add virtio packed ring notification support
+- Add virtio 1.1 server mode support
+- Support crypto Rx and Tx operations on different cores
+- Validate and document basic support for OpenWRT
+- Additional Windows support for EAL functions
### Nice to have - Future {#future}
----
--
2.21.0
next reply other threads:[~2019-12-13 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 11:02 Ferruh Yigit [this message]
2020-01-08 22:13 ` 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=20191213110241.74371-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@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).