From: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
To: pablo.de.lara.guarch@intel.com
Cc: dev@dpdk.org, Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
Subject: [dpdk-dev] [PATCH v6] crypto/aesni_mb: support DOCSIS AES-256
Date: Wed, 15 Apr 2020 12:51:35 +0100 [thread overview]
Message-ID: <1586951495-15679-1-git-send-email-mairtin.oloingsigh@intel.com> (raw)
In-Reply-To: <1586941457-28531-1-git-send-email-mairtin.oloingsigh@intel.com>
This patch adds support for DOCSIS AES-256 when using AESNI-MB
Signed-off-by: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
Acked-by: Pablo de Lara <Pablo.de.lara.guarch@intel.com>
---
This patch depends on these two patches:
v2: Added IPSec MB version check
v3: Added doc update
v4: Added missing patch
v5: Dropping test vector due to refactoring
v6: Fix key size
---
doc/guides/rel_notes/release_20_05.rst | 5 +++++
drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 5 +++++
2 files changed, 10 insertions(+)
diff --git a/doc/guides/rel_notes/release_20_05.rst b/doc/guides/rel_notes/release_20_05.rst
index 6b1a7c58c..72d2f6c27 100644
--- a/doc/guides/rel_notes/release_20_05.rst
+++ b/doc/guides/rel_notes/release_20_05.rst
@@ -81,6 +81,11 @@ New Features
by making use of the event device capabilities. The event mode currently supports
only inline IPsec protocol offload.
+* **Updated the AESNI MB PMD.**
+
+ Updated the AESNI PMD with additional DOCSIS algorithm
+
+ * Added support for AES-256 DOCSIS
Removed Items
-------------
diff --git a/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c b/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c
index 845661174..434e2652b 100644
--- a/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c
+++ b/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c
@@ -314,8 +314,13 @@ static const struct rte_cryptodev_capabilities aesni_mb_pmd_capabilities[] = {
.block_size = 16,
.key_size = {
.min = 16,
+#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
+ .max = 32,
+ .increment = 16
+#else
.max = 16,
.increment = 0
+#endif
},
.iv_size = {
.min = 16,
--
2.12.3
next prev parent reply other threads:[~2020-04-15 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 14:04 [dpdk-dev] [PATCH v3] " Mairtin o Loingsigh
2020-04-10 15:03 ` [dpdk-dev] [PATCH v4 1/2] " Mairtin o Loingsigh
2020-04-14 8:45 ` De Lara Guarch, Pablo
2020-04-15 9:04 ` [dpdk-dev] [PATCH v5] " Mairtin o Loingsigh
2020-04-15 11:07 ` De Lara Guarch, Pablo
2020-04-15 11:51 ` Mairtin o Loingsigh [this message]
2020-04-17 16:31 ` [dpdk-dev] [PATCH v6] " Akhil Goyal
2020-04-17 20:59 ` Akhil Goyal
2020-04-10 15:03 ` [dpdk-dev] [PATCH v4 2/2] test/crypto: Add AES-256 DOCSIS test vectors Mairtin o Loingsigh
2020-04-12 16:43 ` Thomas Monjalon
2020-04-14 8:49 ` De Lara Guarch, Pablo
2020-04-14 9:06 ` Thomas Monjalon
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=1586951495-15679-1-git-send-email-mairtin.oloingsigh@intel.com \
--to=mairtin.oloingsigh@intel.com \
--cc=dev@dpdk.org \
--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).