DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ankur Dwivedi <adwivedi@marvell.com>
To: Didier Pallard <didier.pallard@6wind.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	Anoob Joseph <anoobj@marvell.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	Tejasree Kondoj <ktejasree@marvell.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH v2] crypto/octeontx2: fix crypto OOP support
Date: Thu, 29 Oct 2020 14:38:03 +0000	[thread overview]
Message-ID: <DM5PR1801MB1884A94B417D6A496422B26ADD140@DM5PR1801MB1884.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20201027152058.9598-1-didier.pallard@6wind.com>



>-----Original Message-----
>From: Didier Pallard <didier.pallard@6wind.com>
>Sent: Tuesday, October 27, 2020 8:51 PM
>To: dev@dpdk.org
>Cc: stable@dpdk.org; Ankur Dwivedi <adwivedi@marvell.com>; Anoob Joseph
><anoobj@marvell.com>; Akhil Goyal <akhil.goyal@nxp.com>; Tejasree Kondoj
><ktejasree@marvell.com>
>Subject: [EXT] [PATCH v2] crypto/octeontx2: fix crypto OOP support
>
>External Email
>
>----------------------------------------------------------------------
>Out of place with linear buffers is supported by octeontx2 while not
>advertised.
>
>Fixes: 6aa9ceaddf1d ("crypto/octeontx2: add symmetric capabilities")
>Cc: stable@dpdk.org
>
>Signed-off-by: Didier Pallard <didier.pallard@6wind.com>
Acked-by: Ankur Dwivedi <adwivedi@marvell.com>
>---
>v2:
> * Add documentation.
>
> doc/guides/cryptodevs/features/octeontx2.ini | 1 +
> drivers/crypto/octeontx2/otx2_cryptodev.c    | 1 +
> 2 files changed, 2 insertions(+)
>
>diff --git a/doc/guides/cryptodevs/features/octeontx2.ini
>b/doc/guides/cryptodevs/features/octeontx2.ini
>index c7e418d826e1..b0d50ce98447 100644
>--- a/doc/guides/cryptodevs/features/octeontx2.ini
>+++ b/doc/guides/cryptodevs/features/octeontx2.ini
>@@ -12,6 +12,7 @@ Protocol offload       = Y
> In Place SGL           = Y
> OOP SGL In LB  Out     = Y
> OOP SGL In SGL Out     = Y
>+OOP LB  In LB  Out     = Y
> RSA PRIV OP KEY QT     = Y
> Symmetric sessionless  = Y
>
>diff --git a/drivers/crypto/octeontx2/otx2_cryptodev.c
>b/drivers/crypto/octeontx2/otx2_cryptodev.c
>index 02d2fd83bdcf..44da26c78d04 100644
>--- a/drivers/crypto/octeontx2/otx2_cryptodev.c
>+++ b/drivers/crypto/octeontx2/otx2_cryptodev.c
>@@ -114,6 +114,7 @@ otx2_cpt_pci_probe(struct rte_pci_driver *pci_drv
>__rte_unused,
> 			     RTE_CRYPTODEV_FF_HW_ACCELERATED |
> 			     RTE_CRYPTODEV_FF_SYM_OPERATION_CHAINING
>|
> 			     RTE_CRYPTODEV_FF_IN_PLACE_SGL |
>+			     RTE_CRYPTODEV_FF_OOP_LB_IN_LB_OUT |
> 			     RTE_CRYPTODEV_FF_OOP_SGL_IN_LB_OUT |
> 			     RTE_CRYPTODEV_FF_OOP_SGL_IN_SGL_OUT |
> 			     RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO |
>--
>2.20.1


  parent reply	other threads:[~2020-10-29 14:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 15:50 [dpdk-dev] [PATCH] " Didier Pallard
2020-10-26 18:39 ` Akhil Goyal
2020-10-27 15:20 ` [dpdk-dev] [PATCH v2] " Didier Pallard
2020-10-28 11:52   ` Akhil Goyal
2020-10-29 14:38   ` Ankur Dwivedi [this message]
2020-10-29 14:52     ` [dpdk-dev] [EXT] " Akhil Goyal

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=DM5PR1801MB1884A94B417D6A496422B26ADD140@DM5PR1801MB1884.namprd18.prod.outlook.com \
    --to=adwivedi@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=didier.pallard@6wind.com \
    --cc=ktejasree@marvell.com \
    --cc=stable@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).