DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Vamsi Attunuru <vattunuru@marvell.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>
Subject: Re: [PATCH 1/1] net/cnxk: enable 3des-cbc capability
Date: Sat, 7 May 2022 16:39:00 +0530	[thread overview]
Message-ID: <CALBAE1POF=VtO3-ZEetryu4amB3Mit13Xs6PfuThi1_kpNUiWw@mail.gmail.com> (raw)
In-Reply-To: <20220430045955.1875892-1-vattunuru@marvell.com>

On Sat, Apr 30, 2022 at 10:30 AM Vamsi Attunuru <vattunuru@marvell.com> wrote:
>
> Patch enables 3DES-CBC capability of inline crypto device.
>
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/for-next-net. Thanks

> ---
>  drivers/common/cnxk/cnxk_security.c |  3 +++
>  drivers/net/cnxk/cn10k_ethdev_sec.c | 20 ++++++++++++++++++++
>  2 files changed, 23 insertions(+)
>
> diff --git a/drivers/common/cnxk/cnxk_security.c b/drivers/common/cnxk/cnxk_security.c
> index ec808c0033..8ea0aea7c2 100644
> --- a/drivers/common/cnxk/cnxk_security.c
> +++ b/drivers/common/cnxk/cnxk_security.c
> @@ -129,6 +129,9 @@ ot_ipsec_sa_common_param_fill(union roc_ot_ipsec_sa_word2 *w2,
>                 case RTE_CRYPTO_CIPHER_AES_CTR:
>                         w2->s.enc_type = ROC_IE_OT_SA_ENC_AES_CTR;
>                         break;
> +               case RTE_CRYPTO_CIPHER_3DES_CBC:
> +                       w2->s.enc_type = ROC_IE_OT_SA_ENC_3DES_CBC;
> +                       break;
>                 default:
>                         return -ENOTSUP;
>                 }
> diff --git a/drivers/net/cnxk/cn10k_ethdev_sec.c b/drivers/net/cnxk/cn10k_ethdev_sec.c
> index 87bb691ab4..d0463b3622 100644
> --- a/drivers/net/cnxk/cn10k_ethdev_sec.c
> +++ b/drivers/net/cnxk/cn10k_ethdev_sec.c
> @@ -62,6 +62,26 @@ static struct rte_cryptodev_capabilities cn10k_eth_sec_crypto_caps[] = {
>                         }, }
>                 }, }
>         },
> +       {       /* 3DES CBC */
> +               .op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
> +               {.sym = {
> +                       .xform_type = RTE_CRYPTO_SYM_XFORM_CIPHER,
> +                       {.cipher = {
> +                               .algo = RTE_CRYPTO_CIPHER_3DES_CBC,
> +                               .block_size = 8,
> +                               .key_size = {
> +                                       .min = 24,
> +                                       .max = 24,
> +                                       .increment = 0
> +                               },
> +                               .iv_size = {
> +                                       .min = 8,
> +                                       .max = 16,
> +                                       .increment = 8
> +                               }
> +                       }, }
> +               }, }
> +       },
>         {       /* SHA1 HMAC */
>                 .op = RTE_CRYPTO_OP_TYPE_SYMMETRIC,
>                 {.sym = {
> --
> 2.25.1
>

      reply	other threads:[~2022-05-07 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30  4:59 Vamsi Attunuru
2022-05-07 11:09 ` Jerin Jacob [this message]

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='CALBAE1POF=VtO3-ZEetryu4amB3Mit13Xs6PfuThi1_kpNUiWw@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=thomas@monjalon.net \
    --cc=vattunuru@marvell.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).