DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: John McNamara <john.mcnamara@intel.com>
Cc: web@dpdk.org, dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] update Intel roadmap for 21.08
Date: Tue, 29 Jun 2021 12:12:45 +0200	[thread overview]
Message-ID: <3352678.McnYTdqEyk@thomas> (raw)
In-Reply-To: <20210610185536.1229877-1-john.mcnamara@intel.com>

10/06/2021 20:55, John McNamara:
> Signed-off-by: John McNamara <john.mcnamara@intel.com>
> ---
> --- 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

Applied, thanks.

Note: I removed "Intel" in some lines for consistency with other drivers.



      reply	other threads:[~2021-06-29 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 18:55 John McNamara
2021-06-29 10:12 ` Thomas Monjalon [this message]

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=3352678.McnYTdqEyk@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=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).