DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc: update release notes for 20.05
Date: Mon, 25 May 2020 00:56:19 +0200	[thread overview]
Message-ID: <5018112.LsXbSvgF5q@thomas> (raw)
In-Reply-To: <1590156366-12837-1-git-send-email-john.mcnamara@intel.com>

22/05/2020 16:06, John McNamara:
> +* **Added additional algorithms to the Cryptodev API.**
>  
> +  Added additional algorithms and updated support to the Cryptodev PMD and
> +  APIs, including:
>  
> +  * Added support for intel-ipsec-mb version 0.54 to the following PMDs: AESNI
> +    MB, AESNI GCM, ZUC, KASUMI, SNOW 3G.

These are specific to Intel virtual PMDs, not cryptodev API.

> +  * Added support for Chacha20-Poly1305 AEAD algorithm.
>  
> +  * Updated the ZUC crypto PMD to support Multi-buffer ZUC-EIA3, improving
> +    performance significantly, when using intel-ipsec-mb version 0.54

Same as above


> +  * AESNI MB crypto PMD:
>  
> +    * Updated the AESNI MB PMD with AES-256 DOCSIS algorithm.
> +    * Added support for synchronous Crypto burst API.

Same, all Intel virtual crypto PMDs should be in one category.


>  * **Added handling of mixed crypto algorithms in QAT PMD for GEN2.**
>  
> @@ -212,7 +190,7 @@ New Features
>    when running on GEN2 QAT hardware with particular firmware versions
>    (GEN3 support was added in DPDK 20.02).
>  
> -* **Added plain SHA-1,224,256,384,512 support to QAT PMD.**
> +* **Added plain SHA-1, 224, 256, 384, 512 support to QAT PMD.**
>  
>    Added support for plain SHA-1, SHA-224, SHA-256, SHA-384 and SHA-512 hashes
>    to QAT PMD.
> @@ -220,26 +198,40 @@ New Features
>  * **Added AES-GCM/GMAC J0 support to QAT PMD.**
>  
>    Added support for AES-GCM/GMAC J0 to Intel QuickAssist Technology PMD. User can
> -  use this feature by passing zero length IV in appropriate xform. For more
> -  info please refer to rte_crypto_sym.h J0 comments.
> +  use this feature by passing a zero length IV in the appropriate xform. For more
> +  info refer to the doxygen comments in ``rte_crypto_sym.h`` for ``J0``.
>  
>  * **Updated the QAT PMD for AES-256 DOCSIS.**
>  
> -  Added AES-256 DOCSIS algorithm support to QAT PMD.
> +  Added AES-256 DOCSIS algorithm support to the QAT PMD.
>  
> -* **Added QAT intermediate buffer too small handling in QAT compression PMD.**
> +* **Added QAT intermediate undersized buffer handling in QAT compression PMD.**
>  
> -  Added a special way of buffer handling when internal QAT intermediate buffer
> -  is too small for Huffman dynamic compression operation. Instead of falling
> +  Added special buffer handling when the internal QAT intermediate buffer is
> +  too small for the Huffman dynamic compression operation. Instead of falling
>    back to fixed compression, the operation is now split into multiple smaller
> -  dynamic compression requests (possible to execute on QAT) and their results
> -  are then combined and copied into the output buffer. This is not possible if
> -  any checksum calculation was requested - in such case the code falls back to
> -  fixed compression as before.
> +  dynamic compression requests (which are possible to execute on QAT) and
> +  their results are then combined and copied into the output buffer. This is
> +  not possible if any checksum calculation was requested - in such cases the
> +  code falls back to fixed compression as before.

There are too many separate QAT items.
Can they be grouped in 2 categories (crypto/compress)?


> +* **Added a new driver for Intel Foxville I225 devices.**
> +
> +  Added the new ``igc`` net driver for Intel Foxville I225 devices. See the
> +  :doc:`../nics/igc` NIC guide for more details on this new driver.
> +
> +* **Updated Broadcom bnxt driver.**
> +
> +  Updated the Broadcom bnxt driver with new features and improvements, including:
> +
> +  * Added support for host based flow table management.
> +  * Added flow counters to extended stats.
> +  * Added PCI function stats to extended stats.

The ethdev PMDs should be moved before the cryptodev ones.



  parent reply	other threads:[~2020-05-24 22:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 14:06 John McNamara
2020-05-22 15:17 ` Kevin Traynor
2020-05-25 10:04   ` Mcnamara, John
2020-05-22 15:32 ` Power, Ciara
2020-05-24 22:56 ` Thomas Monjalon [this message]
2020-05-25  9:56   ` Mcnamara, John

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=5018112.LsXbSvgF5q@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    /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).