DPDK patches and discussions
 help / color / mirror / Atom feed
From: Didier Pallard <didier.pallard@6wind.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, Anoob Joseph <anoobj@marvell.com>,
	Srisivasubramanian S <ssrinivasan@caviumnetworks.com>,
	Ankur Dwivedi <ankur.dwivedi@caviumnetworks.com>,
	Murthy NSSR <nidadavolu.murthy@caviumnetworks.com>,
	Nithin Dabilpuram <nithin.dabilpuram@caviumnetworks.com>,
	Ragothaman Jayaraman <rjayaraman@caviumnetworks.com>
Subject: [dpdk-dev] [PATCH] crypto/octeontx: fix crypto OOP support
Date: Fri, 23 Oct 2020 17:48:46 +0200	[thread overview]
Message-ID: <20201023154846.27698-1-didier.pallard@6wind.com> (raw)

Out of place with linear buffers is supported by octeontx
while not advertised.

Cc: stable@dpdk.org
Fixes: 0dc1cffa4d33 ("crypto/octeontx: add hardware init routine")
Signed-off-by: Didier Pallard <didier.pallard@6wind.com>
---
 drivers/crypto/octeontx/otx_cryptodev_ops.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/crypto/octeontx/otx_cryptodev_ops.c b/drivers/crypto/octeontx/otx_cryptodev_ops.c
index 14f22e3011a0..05d6dfff7c5a 100644
--- a/drivers/crypto/octeontx/otx_cryptodev_ops.c
+++ b/drivers/crypto/octeontx/otx_cryptodev_ops.c
@@ -985,6 +985,7 @@ otx_cpt_dev_create(struct rte_cryptodev *c_dev)
 				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_SYM_SESSIONLESS;
-- 
2.20.1


             reply	other threads:[~2020-10-23 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 15:48 Didier Pallard [this message]
2020-10-27 15:19 ` [dpdk-dev] [PATCH v2] " Didier Pallard
2020-10-29 14:36   ` [dpdk-dev] [dpdk-stable] " Ankur Dwivedi
2020-10-29 14:51   ` [dpdk-dev] " 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=20201023154846.27698-1-didier.pallard@6wind.com \
    --to=didier.pallard@6wind.com \
    --cc=ankur.dwivedi@caviumnetworks.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=nidadavolu.murthy@caviumnetworks.com \
    --cc=nithin.dabilpuram@caviumnetworks.com \
    --cc=rjayaraman@caviumnetworks.com \
    --cc=ssrinivasan@caviumnetworks.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).