From: Shijith Thotton <sthotton@marvell.com>
To: Boris Brezillon <bbrezillon@kernel.org>,
Arnaud Ebalard <arno@natisbad.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: Shijith Thotton <sthotton@marvell.com>,
<linux-crypto@vger.kernel.org>, <jerinj@marvell.com>,
<sgoutham@marvell.com>, <gcherian@marvell.com>,
<ndabilpuram@marvell.com>, <schalla@marvell.com>
Subject: [PATCH 0/2] Octeon TX2 CPT custom engine group
Date: Wed, 1 Dec 2021 14:31:59 +0530 [thread overview]
Message-ID: <cover.1638348922.git.sthotton@marvell.com> (raw)
Octeon TX2 CPT has three type of engines to handle symmetric, asymmetric
and ipsec specific workload. For better utilization, these engines can
be grouped to custom groups at runtime. Devlink parameters are used to
create and destroy the custom groups (devlink is a framework mainly used
in network subsystem).
Srujana Challa (2):
crypto: octeontx2: add apis for custom engine groups
crypto: octeontx2: parameters for custom engine groups
drivers/crypto/marvell/octeontx2/Makefile | 2 +-
.../marvell/octeontx2/otx2_cpt_common.h | 1 +
.../marvell/octeontx2/otx2_cpt_devlink.c | 108 ++++++
.../marvell/octeontx2/otx2_cpt_devlink.h | 20 ++
drivers/crypto/marvell/octeontx2/otx2_cptpf.h | 3 +
.../marvell/octeontx2/otx2_cptpf_main.c | 9 +
.../marvell/octeontx2/otx2_cptpf_ucode.c | 322 +++++++++++++++++-
.../marvell/octeontx2/otx2_cptpf_ucode.h | 7 +-
8 files changed, 464 insertions(+), 8 deletions(-)
create mode 100644 drivers/crypto/marvell/octeontx2/otx2_cpt_devlink.c
create mode 100644 drivers/crypto/marvell/octeontx2/otx2_cpt_devlink.h
--
2.25.1
next reply other threads:[~2021-12-01 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 9:01 Shijith Thotton [this message]
2021-12-01 9:02 ` [PATCH 1/2] crypto: octeontx2: add apis for custom engine groups Shijith Thotton
2021-12-01 9:02 ` [PATCH 2/2] crypto: octeontx2: parameters " Shijith Thotton
2021-12-11 5:56 ` [PATCH 0/2] Octeon TX2 CPT custom engine group Herbert Xu
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=cover.1638348922.git.sthotton@marvell.com \
--to=sthotton@marvell.com \
--cc=arno@natisbad.org \
--cc=bbrezillon@kernel.org \
--cc=gcherian@marvell.com \
--cc=herbert@gondor.apana.org.au \
--cc=jerinj@marvell.com \
--cc=linux-crypto@vger.kernel.org \
--cc=ndabilpuram@marvell.com \
--cc=schalla@marvell.com \
--cc=sgoutham@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.