DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shijith Thotton <sthotton@marvell.com>
To: <dev@dpdk.org>
Cc: <sthotton@marvell.com>, <pbhagavatula@marvell.com>,
	<anoobj@marvell.com>,  <jerinj@marvell.com>,
	<abhinandan.gujjar@intel.com>, <adwivedi@marvell.com>,
	<gakhil@marvell.com>
Subject: [dpdk-dev] [PATCH 0/2] OCTEONTX crypto adapter support
Date: Tue, 22 Jun 2021 22:18:07 +0530	[thread overview]
Message-ID: <cover.1624379833.git.sthotton@marvell.com> (raw)

Below patches add crypto adapter OP_FORWARD support for OCTEON TX PMD.

Shijith Thotton (2):
  drivers: add octeontx crypto adapter framework
  drivers: add octeontx crypto adapter data path

 doc/guides/rel_notes/release_21_08.rst        |   4 +
 drivers/common/cpt/cpt_common.h               |   2 +-
 drivers/crypto/octeontx/meson.build           |   6 +
 drivers/crypto/octeontx/otx_cryptodev.c       |   4 +
 drivers/crypto/octeontx/otx_cryptodev.h       |   4 -
 .../crypto/octeontx/otx_cryptodev_hw_access.h |   1 +
 drivers/crypto/octeontx/otx_cryptodev_ops.c   | 272 +++++++++++++-----
 drivers/crypto/octeontx/otx_cryptodev_ops.h   |   7 +
 drivers/crypto/octeontx/version.map           |   9 +
 drivers/event/octeontx/meson.build            |   1 +
 drivers/event/octeontx/ssovf_evdev.c          |  68 +++++
 drivers/event/octeontx/ssovf_worker.c         |  11 +
 drivers/event/octeontx/ssovf_worker.h         |  25 +-
 .../octeontx2/otx2_evdev_crypto_adptr_rx.h    |   6 +-
 14 files changed, 332 insertions(+), 88 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-06-22 16:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 16:48 Shijith Thotton [this message]
2021-06-22 16:48 ` [dpdk-dev] [PATCH 1/2] drivers: add octeontx crypto adapter framework Shijith Thotton
2021-06-22 16:48 ` [dpdk-dev] [PATCH 2/2] drivers: add octeontx crypto adapter data path Shijith Thotton
2021-07-06 20:20   ` Akhil Goyal
2021-06-23 20:53 ` [dpdk-dev] [PATCH v2 0/2] OCTEONTX crypto adapter support Shijith Thotton
2021-06-23 20:53   ` [dpdk-dev] [PATCH v2 1/2] drivers: add octeontx crypto adapter framework Shijith Thotton
2021-07-06 20:14     ` Akhil Goyal
2021-07-15 14:21     ` David Marchand
2021-07-16  8:39       ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-20 11:58         ` Akhil Goyal
2021-07-20 12:14           ` David Marchand
2021-07-21  9:44             ` Thomas Monjalon
2021-07-21 15:11               ` Brandon Lo
2021-07-22  7:45               ` Akhil Goyal
2021-07-22  9:06                 ` [dpdk-dev] [PATCH] crypto/octeontx: enable build on non Linux OS Shijith Thotton
2021-07-22  9:17                   ` Akhil Goyal
2021-07-22 19:06                     ` Thomas Monjalon
2021-07-22 19:08                       ` Thomas Monjalon
2021-07-22 20:20                         ` Brandon Lo
2021-07-22 20:32                           ` Thomas Monjalon
2021-06-23 20:53   ` [dpdk-dev] [PATCH v2 2/2] drivers: add octeontx crypto adapter data path Shijith Thotton
2021-06-30  8:54     ` Akhil Goyal
2021-06-30 16:23       ` [dpdk-dev] [dpdk-ci] " Brandon Lo
2021-07-07  9:28   ` [dpdk-dev] [PATCH v2 0/2] OCTEONTX crypto adapter support 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=cover.1624379833.git.sthotton@marvell.com \
    --to=sthotton@marvell.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@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).