From: Tejasree Kondoj <ktejasree@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Tejasree Kondoj <ktejasree@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Archana Muniganti <marchana@marvell.com>,
Srujana Challa <schalla@marvell.com>,
"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
Jerin Jacob <jerinj@marvell.com>, <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 0/8] add lookaside IPsec additional features
Date: Tue, 31 Aug 2021 19:31:19 +0530 [thread overview]
Message-ID: <20210831140127.31775-1-ktejasree@marvell.com> (raw)
This series adds cn10k lookaside IPsec AES-CBC-HMAC-SHA1, UDP encapsulation
and transport mode support along with common cnxk pmd changes.
The functionality has been tested with ipsec-secgw application running in
lookaside protocol offload mode.
Archana Muniganti (2):
crypto/cnxk: make IPsec verify functions common
common/cnxk: make IPsec defines common
Tejasree Kondoj (6):
common/cnxk: add hash generation APIs
crypto/cnxk: add lookaside IPsec AES-CBC-HMAC-SHA1 support
crypto/cnxk: remove redundant code
crypto/cnxk: use rlen from CPT result with lookaside
crypto/cnxk: support cn10k transport mode
crypto/cnxk: support UDP encap with lookaside IPsec
doc/guides/cryptodevs/cnxk.rst | 3 +
doc/guides/rel_notes/release_21_11.rst | 6 +
drivers/common/cnxk/cnxk_security.c | 92 +++++-
drivers/common/cnxk/meson.build | 1 +
drivers/common/cnxk/roc_api.h | 4 +
drivers/common/cnxk/roc_hash.c | 275 ++++++++++++++++++
drivers/common/cnxk/roc_hash.h | 16 +
drivers/common/cnxk/roc_ie.h | 33 ++-
drivers/common/cnxk/roc_ie_on.h | 26 --
drivers/common/cnxk/roc_ie_ot.h | 26 --
drivers/common/cnxk/version.map | 3 +
drivers/crypto/cnxk/cn10k_cryptodev_ops.c | 44 +--
drivers/crypto/cnxk/cn10k_ipsec.c | 64 +---
drivers/crypto/cnxk/cn10k_ipsec.h | 6 +-
drivers/crypto/cnxk/cn10k_ipsec_la_ops.h | 28 +-
drivers/crypto/cnxk/cnxk_cryptodev.h | 2 +-
.../crypto/cnxk/cnxk_cryptodev_capabilities.c | 79 ++++-
drivers/crypto/cnxk/cnxk_ipsec.h | 114 ++++++++
18 files changed, 620 insertions(+), 202 deletions(-)
create mode 100644 drivers/common/cnxk/roc_hash.c
create mode 100644 drivers/common/cnxk/roc_hash.h
--
2.27.0
next reply other threads:[~2021-08-31 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 14:01 Tejasree Kondoj [this message]
2021-08-31 14:01 ` [dpdk-dev] [PATCH 1/8] common/cnxk: add hash generation APIs Tejasree Kondoj
2021-08-31 14:01 ` [dpdk-dev] [PATCH 2/8] crypto/cnxk: add lookaside IPsec AES-CBC-HMAC-SHA1 support Tejasree Kondoj
2021-08-31 14:01 ` [dpdk-dev] [PATCH 3/8] crypto/cnxk: remove redundant code Tejasree Kondoj
2021-08-31 14:01 ` [dpdk-dev] [PATCH 4/8] crypto/cnxk: use rlen from CPT result with lookaside Tejasree Kondoj
2021-08-31 14:01 ` [dpdk-dev] [PATCH 5/8] crypto/cnxk: make IPsec verify functions common Tejasree Kondoj
2021-08-31 14:01 ` [dpdk-dev] [PATCH 6/8] crypto/cnxk: support cn10k transport mode Tejasree Kondoj
2021-08-31 14:01 ` [dpdk-dev] [PATCH 7/8] crypto/cnxk: support UDP encap with lookaside IPsec Tejasree Kondoj
2021-08-31 14:01 ` [dpdk-dev] [PATCH 8/8] common/cnxk: make IPsec defines common Tejasree Kondoj
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=20210831140127.31775-1-ktejasree@marvell.com \
--to=ktejasree@marvell.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=marchana@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=schalla@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).