DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Cc: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] [PATCH] doc: fix incomplete crypto dev matrices
Date: Wed, 18 Jan 2017 17:35:48 +0000	[thread overview]
Message-ID: <1484760948-136116-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)

When ZUC PMD was added, it was not added in the
Crypto Device Supported Functionality Matrices.
This commit adds a column in all the matrices, plus
the ZUC EEA3/EIA3 algorithms.

Fixes: cf7685d68f00 ("crypto/zuc: add driver for ZUC library")

Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
 doc/guides/cryptodevs/overview.rst | 88 +++++++++++++++++++-------------------
 1 file changed, 45 insertions(+), 43 deletions(-)

diff --git a/doc/guides/cryptodevs/overview.rst b/doc/guides/cryptodevs/overview.rst
index 8e03cdd..bd5f0ad 100644
--- a/doc/guides/cryptodevs/overview.rst
+++ b/doc/guides/cryptodevs/overview.rst
@@ -33,66 +33,68 @@ Crypto Device Supported Functionality Matrices
 Supported Feature Flags
 
 .. csv-table::
-   :header: "Feature Flags", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi"
+   :header: "Feature Flags", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi", "zuc"
    :stub-columns: 1
 
-   "RTE_CRYPTODEV_FF_SYMMETRIC_CRYPTO",x,x,x,x,x,x
-   "RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO",,,,,,
-   "RTE_CRYPTODEV_FF_SYM_OPERATION_CHAINING",x,x,x,x,x,x
-   "RTE_CRYPTODEV_FF_CPU_SSE",,,x,,x,x
-   "RTE_CRYPTODEV_FF_CPU_AVX",,,x,,x,x
-   "RTE_CRYPTODEV_FF_CPU_AVX2",,,x,,,
-   "RTE_CRYPTODEV_FF_CPU_AVX512",,,x,,,
-   "RTE_CRYPTODEV_FF_CPU_AESNI",,,x,x,,
-   "RTE_CRYPTODEV_FF_HW_ACCELERATED",x,,,,,
+   "RTE_CRYPTODEV_FF_SYMMETRIC_CRYPTO",x,x,x,x,x,x,x
+   "RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO",,,,,,,
+   "RTE_CRYPTODEV_FF_SYM_OPERATION_CHAINING",x,x,x,x,x,x,x
+   "RTE_CRYPTODEV_FF_CPU_SSE",,,x,,x,x,
+   "RTE_CRYPTODEV_FF_CPU_AVX",,,x,,x,x,
+   "RTE_CRYPTODEV_FF_CPU_AVX2",,,x,,,,
+   "RTE_CRYPTODEV_FF_CPU_AVX512",,,x,,,,
+   "RTE_CRYPTODEV_FF_CPU_AESNI",,,x,x,,,
+   "RTE_CRYPTODEV_FF_HW_ACCELERATED",x,,,,,,
 
 Supported Cipher Algorithms
 
 .. csv-table::
-   :header: "Cipher Algorithms", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi"
+   :header: "Cipher Algorithms", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi", "zuc"
    :stub-columns: 1
 
-   "NULL",,x,,,,
-   "AES_CBC_128",x,,x,,,
-   "AES_CBC_192",x,,x,,,
-   "AES_CBC_256",x,,x,,,
-   "AES_CTR_128",x,,x,,,
-   "AES_CTR_192",x,,x,,,
-   "AES_CTR_256",x,,x,,,
-   "DES_CBC",x,,,,,
-   "SNOW3G_UEA2",x,,,,x,
-   "KASUMI_F8",,,,,,x
+   "NULL",,x,,,,,
+   "AES_CBC_128",x,,x,,,,
+   "AES_CBC_192",x,,x,,,,
+   "AES_CBC_256",x,,x,,,,
+   "AES_CTR_128",x,,x,,,,
+   "AES_CTR_192",x,,x,,,,
+   "AES_CTR_256",x,,x,,,,
+   "DES_CBC",x,,,,,,
+   "SNOW3G_UEA2",x,,,,x,,
+   "KASUMI_F8",,,,,,x,
+   "ZUC_EEA3",,,,,,,x
 
 Supported Authentication Algorithms
 
 .. csv-table::
-   :header: "Cipher Algorithms", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi"
+   :header: "Cipher Algorithms", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi", "zuc"
    :stub-columns: 1
 
-   "NONE",,x,,,,
-   "MD5",,,,,,
-   "MD5_HMAC",,,x,,,
-   "SHA1",,,,,,
-   "SHA1_HMAC",x,,x,,,
-   "SHA224",,,,,,
-   "SHA224_HMAC",,,x,,,
-   "SHA256",,,,,,
-   "SHA256_HMAC",x,,x,,,
-   "SHA384",,,,,,
-   "SHA384_HMAC",,,x,,,
-   "SHA512",,,,,,
-   "SHA512_HMAC",x,,x,,,
-   "AES_XCBC",x,,x,,,
-   "AES_GMAC",,,,x,,
-   "SNOW3G_UIA2",x,,,,x,
-   "KASUMI_F9",,,,,,x
+   "NONE",,x,,,,,
+   "MD5",,,,,,,
+   "MD5_HMAC",,,x,,,,
+   "SHA1",,,,,,,
+   "SHA1_HMAC",x,,x,,,,
+   "SHA224",,,,,,,
+   "SHA224_HMAC",,,x,,,,
+   "SHA256",,,,,,,
+   "SHA256_HMAC",x,,x,,,,
+   "SHA384",,,,,,,
+   "SHA384_HMAC",,,x,,,,
+   "SHA512",,,,,,,
+   "SHA512_HMAC",x,,x,,,,
+   "AES_XCBC",x,,x,,,,
+   "AES_GMAC",,,,x,,,
+   "SNOW3G_UIA2",x,,,,x,,
+   "KASUMI_F9",,,,,,x,
+   "ZUC_EIA3",,,,,,,x
 
 Supported AEAD Algorithms
 
 .. csv-table::
-   :header: "AEAD Algorithms", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi"
+   :header: "AEAD Algorithms", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi", "zuc"
    :stub-columns: 1
 
-   "AES_GCM_128",x,,,x,,
-   "AES_GCM_192",x,,,,,
-   "AES_GCM_256",x,,,x,,
+   "AES_GCM_128",x,,,x,,,
+   "AES_GCM_192",x,,,,,,
+   "AES_GCM_256",x,,,x,,,
-- 
2.7.4

             reply	other threads:[~2017-01-18 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 17:35 Pablo de Lara [this message]
2017-01-27 16:27 ` De Lara Guarch, Pablo

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=1484760948-136116-1-git-send-email-pablo.de.lara.guarch@intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@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).