diff mbox series

crypto/mvsam: add comments for three crypto devs

Message ID 20210701070005.31140-1-danat@marvell.com (mailing list archive)
State Accepted, archived
Delegated to: akhil goyal
Headers
Series crypto/mvsam: add comments for three crypto devs |

Checks

Context Check Description
ci/checkpatch success coding style OK
ci/github-robot success github build: passed
ci/iol-intel-Functional success Functional Testing PASS
ci/iol-testing fail Testing issues
ci/Intel-compilation success Compilation OK
ci/intel-Testing success Testing PASS
ci/iol-intel-Performance fail Performance Testing issues
ci/iol-mellanox-Functional fail Functional Testing issues
ci/iol-abi-testing success Testing PASS

Commit Message

danat@marvell.com July 1, 2021, 7 a.m. UTC 
  From: Michael Shamis <michaelsh@marvell.com>

Till now comments explain queue mapping per
one and two crypto devices.
Now added comments for queue mapping for three
crypto devices supported in CN9132.

Signed-off-by: Michael Shamis <michaelsh@marvell.com>
Reviewed-by: Liron Himi <lironh@marvell.com>
---
 drivers/crypto/mvsam/rte_mrvl_pmd_ops.c | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

Comments

Akhil Goyal July 7, 2021, 3:51 p.m. UTC | #1 
> From: Michael Shamis <michaelsh@marvell.com>
> 
> Till now comments explain queue mapping per
> one and two crypto devices.
> Now added comments for queue mapping for three
> crypto devices supported in CN9132.
> 
> Signed-off-by: Michael Shamis <michaelsh@marvell.com>
> Reviewed-by: Liron Himi <lironh@marvell.com>
> ---
Applied to dpdk-next-crypto

Thanks.
Akhil Goyal July 7, 2021, 3:57 p.m. UTC | #2 
> 
> Till now comments explain queue mapping per
> one and two crypto devices.
> Now added comments for queue mapping for three
> crypto devices supported in CN9132.
> 
> Signed-off-by: Michael Shamis <michaelsh@marvell.com>
> Reviewed-by: Liron Himi <lironh@marvell.com>
> ---
Applied to dpdk-next-crypto

Title updated as " crypto/mvsam: update comments for qp mapping"
diff mbox series

Patch

diff --git a/drivers/crypto/mvsam/rte_mrvl_pmd_ops.c b/drivers/crypto/mvsam/rte_mrvl_pmd_ops.c
index 1a0a9fc14..75bb8adb8 100644
--- a/drivers/crypto/mvsam/rte_mrvl_pmd_ops.c
+++ b/drivers/crypto/mvsam/rte_mrvl_pmd_ops.c
@@ -663,6 +663,11 @@  mrvl_crypto_pmd_qp_setup(struct rte_cryptodev *dev, uint16_t qp_id,
 		}
 
 		/*
+		 * In case just one engine is enabled mapping will look as
+		 * follows:
+		 * qp:      0        1        2        3
+		 * cio-x:y: cio-0:0, cio-0:1, cio-0:2, cio-0:3
+		 *
 		 * In case two crypto engines are enabled qps will
 		 * be evenly spread among them. Even and odd qps will
 		 * be handled by cio-0 and cio-1 respectively. qp-cio mapping
@@ -674,10 +679,17 @@  mrvl_crypto_pmd_qp_setup(struct rte_cryptodev *dev, uint16_t qp_id,
 		 * qp:      4        5        6        7
 		 * cio-x:y: cio-0:2, cio-1:2, cio-0:3, cio-1:3
 		 *
-		 * In case just one engine is enabled mapping will look as
-		 * follows:
+		 * In case of three crypto engines are enabled qps will
+		 * be mapped as following:
+		 *
 		 * qp:      0        1        2        3
-		 * cio-x:y: cio-0:0, cio-0:1, cio-0:2, cio-0:3
+		 * cio-x:y: cio-0:0, cio-1:0, cio-2:0, cio-0:1
+		 *
+		 * qp:      4        5        6        7
+		 * cio-x:y: cio-1:1, cio-2:1, cio-0:2, cio-1:2
+		 *
+		 * qp:      8        9        10       11
+		 * cio-x:y: cio-2:2, cio-0:3, cio-1:3, cio-2:3
 		 */
 		n = snprintf(match, sizeof(match), "cio-%u:%u",
 				qp_id % num, qp_id / num);