DPDK patches and discussions
 help / color / mirror / Atom feed
From: Adam Dybkowski <adamx.dybkowski@intel.com>
To: dev@dpdk.org, fiona.trahe@intel.com, akhil.goyal@nxp.com
Cc: Adam Dybkowski <adamx.dybkowski@intel.com>
Subject: [dpdk-dev] [PATCH v3 2/2] doc: update QAT PMD release notes
Date: Thu, 16 Jul 2020 13:47:23 +0200	[thread overview]
Message-ID: <20200716114723.965-3-adamx.dybkowski@intel.com> (raw)
In-Reply-To: <20200716114723.965-1-adamx.dybkowski@intel.com>

This patch separates QAT PMD paragraphs in the release notes
into three parts, for QAT Symmetric Crypto PMD, QAT Asymmetric
Crypto PMD and QAT Compression PMD.

Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
---
 doc/guides/rel_notes/release_20_08.rst | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/doc/guides/rel_notes/release_20_08.rst b/doc/guides/rel_notes/release_20_08.rst
index e598d4882..da2833170 100644
--- a/doc/guides/rel_notes/release_20_08.rst
+++ b/doc/guides/rel_notes/release_20_08.rst
@@ -185,7 +185,7 @@ New Features
   Added support for lookaside protocol offload for DOCSIS through the
   ``rte_security`` API.
 
-* **Updated the QuickAssist Technology (QAT) PMD.**
+* **Updated the QuickAssist Technology (QAT) Symmetric Crypto PMD.**
 
   * Added support for lookaside protocol offload for DOCSIS through the
     ``rte_security`` API.
@@ -194,6 +194,14 @@ New Features
   * Added support for Intel GEN2 QuickAssist device 200xx
   (PF Did 0x18ee, VF Did 0x18ef).
 
+* **Updated the QuickAssist Technology (QAT) Asymmetric Crypto PMD.**
+
+  * Improved handling of multi process in QAT crypto and compression PMDs.
+
+* **Updated the QuickAssist Technology (QAT) Compression PMD.**
+
+  * Improved handling of multi process in QAT crypto and compression PMDs.
+
 * **Updated the OCTEON TX2 crypto PMD.**
 
   Added Chacha20-Poly1305 AEAD algorithm support in OCTEON TX2 crypto PMD.
-- 
2.25.1


  parent reply	other threads:[~2020-07-16 11:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 12:29 [dpdk-dev] [PATCH] common/qat: support GEN2 device C34xx Adam Dybkowski
2020-07-13 11:09 ` [dpdk-dev] [PATCH v2 0/1] common/qat: support GEN2 QAT device 200xx Adam Dybkowski
2020-07-13 11:09   ` [dpdk-dev] [PATCH v2 1/1] " Adam Dybkowski
2020-07-13 15:27     ` Trahe, Fiona
2020-07-16 11:47   ` [dpdk-dev] [PATCH v3 0/2] " Adam Dybkowski
2020-07-16 11:47     ` [dpdk-dev] [PATCH v3 1/2] " Adam Dybkowski
2020-07-16 11:47     ` Adam Dybkowski [this message]
2020-07-16 16:54       ` [dpdk-dev] [PATCH v3 2/2] doc: update QAT PMD release notes Akhil Goyal
2020-07-22  8:07     ` [dpdk-dev] [PATCH v4 0/1] common/qat: support GEN2 QAT device 200xx Adam Dybkowski
2020-07-22  8:07       ` [dpdk-dev] [PATCH v4 1/1] " Adam Dybkowski
2020-07-22 11:05         ` Trahe, Fiona
2020-07-26 18:45         ` Akhil Goyal
2020-07-27 10:14       ` [dpdk-dev] [PATCH v5 0/2] " Adam Dybkowski
2020-07-27 10:14         ` [dpdk-dev] [PATCH v5 1/2] " Adam Dybkowski
2020-07-27 10:14         ` [dpdk-dev] [PATCH v5 2/2] doc: update QAT PMD release notes Adam Dybkowski
2020-07-28 22:16           ` Thomas Monjalon
2020-07-28 20:05         ` [dpdk-dev] [PATCH v5 0/2] common/qat: support GEN2 QAT device 200xx Akhil Goyal

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=20200716114723.965-3-adamx.dybkowski@intel.com \
    --to=adamx.dybkowski@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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).