From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "O'loingsigh, Mairtin" <mairtin.oloingsigh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 1/2] crypto/aesni_mb: support DOCSIS AES-256
Date: Tue, 14 Apr 2020 08:45:31 +0000 [thread overview]
Message-ID: <SN6PR11MB31017969B0A03335B676398084DA0@SN6PR11MB3101.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1586531010-32279-1-git-send-email-mairtin.oloingsigh@intel.com>
Hi Mairtin,
> -----Original Message-----
> From: O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> Sent: Friday, April 10, 2020 4:03 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> Subject: [PATCH v4 1/2] crypto/aesni_mb: support DOCSIS AES-256
>
> 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>
> ---
> v2: Added IPSec MB version check
> v3: Added doc update
> v4: Added missing patch
> ---
> doc/guides/rel_notes/release_20_05.rst | 5 +++++
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 6 ++++++
> 2 files changed, 11 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..0d555ec29 100644
> --- a/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c
> +++ b/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c
> @@ -319,8 +319,14 @@ static const struct rte_cryptodev_capabilities
> aesni_mb_pmd_capabilities[] = {
> },
> .iv_size = {
> .min = 16,
> +#if IMB_VERSION_NUM >= IMB_VERSION(0, 53, 3)
> + .max = 32,
> + .increment = 16
> +#else
> .max = 16,
> .increment = 0
> +#endif
Apologies, I missed this earlier and I just realized this is wrong.
This should be done in key_size, not iv_size.
Thanks,
Pablo
> +
> }
> }, }
> }, }
> --
> 2.12.3
next prev parent reply other threads:[~2020-04-14 8:45 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 [this message]
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 ` [dpdk-dev] [PATCH v6] " Mairtin o Loingsigh
2020-04-17 16:31 ` 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=SN6PR11MB31017969B0A03335B676398084DA0@SN6PR11MB3101.namprd11.prod.outlook.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=mairtin.oloingsigh@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).