DPDK patches and discussions
 help / color / mirror / Atom feed
From: John McNamara <john.mcnamara@intel.com>
To: web@dpdk.org
Cc: dev@dpdk.org, thomas@monjalon.net, ferruh.yigit@intel.com,
	John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] [PATCH v1] update Intel roadmap for 21.08
Date: Thu, 10 Jun 2021 18:55:36 +0000	[thread overview]
Message-ID: <20210610185536.1229877-1-john.mcnamara@intel.com> (raw)

Signed-off-by: John McNamara <john.mcnamara@intel.com>
---
 content/roadmap/_index.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index d77bbd7..6b389f1 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -15,19 +15,25 @@ This list is obviously neither complete nor guaranteed.
 - Arm CRC32 in generic API
 - Aarch32 cross-compilation support
 <!-- Networking -->
+- IAVF PMD support for Windows
 - Tx QoS marking API
 - AVF software back-end driver with device emulation libraries
 <!-- Network drivers -->
+- Intel ice PMD support for ETS based HQoS for VF
+- Intel ice PMD support for FDIR/RSS on GTP over GRE for VF
 - mlx5 inline IPsec ESP crypto
+- multi-queue capability for PMD power enhancements
 - octeontx2 mirroring
 - octeontx3 driver for ethdev and rte_flow support
 - qede initial support for next generation hardware
 - qede flow API support
 - Wangxun driver for 1Gb NICs
 <!-- Virtualisation -->
+- enhanced async support for vhost library
 <!-- Network apps -->
 - testpmd multi-process support
 <!-- Crypto -->
+- Intel QuickAssist symmetric crypto driver for fourth generation devices
 - mlx5 AES-XTS look-aside crypto
 <!-- Compress -->
 <!-- Event -->
-- 
2.25.1


             reply	other threads:[~2021-06-10 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 18:55 John McNamara [this message]
2021-06-29 10:12 ` 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=20210610185536.1229877-1-john.mcnamara@intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).