DPDK patches and discussions
 help / color / mirror / Atom feed
From: <danat@marvell.com>
To: <gakhil@marvell.com>
Cc: <dev@dpdk.org>, <danat@marvell.com>, <lironh@marvell.com>,
	<michaelsh@marvell.com>
Subject: [dpdk-dev] [PATCH] crypto/mvsam: add comments for three crypto devs
Date: Thu, 1 Jul 2021 10:00:05 +0300	[thread overview]
Message-ID: <20210701070005.31140-1-danat@marvell.com> (raw)

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(-)

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);
-- 
2.17.1


             reply	other threads:[~2021-07-01  7:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01  7:00 danat [this message]
2021-07-07 15:51 ` Akhil Goyal
2021-07-07 15:57 ` 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=20210701070005.31140-1-danat@marvell.com \
    --to=danat@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=lironh@marvell.com \
    --cc=michaelsh@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).