From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Fiona Trahe <fiona.trahe@intel.com>,
pablo.de.lara.guarch@intel.com, deepak.k.jain@intel.com
Cc: dev@dpdk.org, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: fix crypto overview matrix for missing QAT items
Date: Thu, 09 Mar 2017 21:20:22 +0100 [thread overview]
Message-ID: <4292064.idvsfVglIt@xps13> (raw)
In-Reply-To: <1488545508-8110-1-git-send-email-fiona.trahe@intel.com>
2017-03-03 12:51, Fiona Trahe:
> Support for all the following was added in release 16.11
> but not updated in the matrix:
> 3DES, MD5_HMAC, SHA224, SHA383, NULL, KASUMI F8/F9, GMAC.
>
> Fixes: e1b7f509e6f2 ("crypto/qat: add 3DES cipher algorithm")
> Fixes: 61ec5181625f ("crypto/qat: add MD5 HMAC capability")
> Fixes: ebdbe12fbfc1 ("crypto/qat: add aes-sha224-hmac capability")
> Fixes: d905ee32d0dc ("crypto/qat: add aes-sha384-hmac capability")
> Fixes: db0e952a5c01 ("crypto/qat: add NULL capability")
> Fixes: d4f2745300e0 ("crypto/qat: add KASUMI")
> Fixes: 2fa64f840d65 ("crypto/qat: add GMAC capability")
There was already a miss for ZUC added in previous release.
It is hard to maintain such matrix...
>
> - "NULL",,x,,,,,,
> + "NULL",x,x,,,,,,
> "AES_CBC_128",x,,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,,,,,
> + "3DES_CBC",x,,,,,,,
> + "3DES_CTR",x,,,,,,,
> "DES_CBC",x,,,,,,,
> "SNOW3G_UEA2",x,,,,x,,,
> - "KASUMI_F8",,,,,,x,,
> + "KASUMI_F8",x,,,,,x,,
> "ZUC_EEA3",,,,,,,x,
> "AES_DOCSISBPI",x,,,,,,,
> "DES_DOCSISBPI",x,,,,,,,
... and even harder when it so unreadable!
Please switch to the features directory system used for networking drivers.
next prev parent reply other threads:[~2017-03-09 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 12:51 Fiona Trahe
2017-03-09 20:20 ` Thomas Monjalon [this message]
2017-03-22 16:19 ` 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=4292064.idvsfVglIt@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.mcnamara@intel.com \
--cc=pablo.de.lara.guarch@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).