DPDK patches and discussions
 help / color / mirror / Atom feed
From: Archana Muniganti <marchana@marvell.com>
To: <gakhil@marvell.com>
Cc: Archana Muniganti <marchana@marvell.com>, <ktejasree@marvell.com>,
	<adwivedi@marvell.com>, <anoobj@marvell.com>,
	<jerinj@marvell.com>, <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 0/8] add cn9k lookaside IPsec support
Date: Thu, 2 Sep 2021 19:12:46 +0530	[thread overview]
Message-ID: <20210902134254.28373-1-marchana@marvell.com> (raw)

This series adds lookaside IPsec support in crypto_cn9k PMD.

Depends on:
http://patches.dpdk.org/project/dpdk/list/?series=18628

Archana Muniganti (8):
  crypto/cnxk: add cn9k security ctx
  common/cnxk: add cn9k IPsec microcode defines
  crypto/cnxk: add cn9k IPsec session related functions
  crypto/cnxk: add cn9k IPsec outbound session create function
  crypto/cnxk: add cn9k IPsec inbound session create function
  crypto/cnxk: add cn9k lookaside IPsec datapath
  crypto/cnxk: update tailroom requirement
  crypto/cnxk: update feature flag for cn9k lookaside IPsec

 doc/guides/cryptodevs/cnxk.rst           |  14 +-
 doc/guides/cryptodevs/features/cn9k.ini  |   1 +
 doc/guides/rel_notes/release_21_11.rst   |   3 +
 drivers/common/cnxk/roc_cpt.h            |   1 +
 drivers/common/cnxk/roc_ie_on.h          | 158 +++++-
 drivers/crypto/cnxk/cn9k_cryptodev.c     |  11 +
 drivers/crypto/cnxk/cn9k_cryptodev_ops.c |  78 ++-
 drivers/crypto/cnxk/cn9k_ipsec.c         | 612 +++++++++++++++++++++++
 drivers/crypto/cnxk/cn9k_ipsec.h         |  46 ++
 drivers/crypto/cnxk/cn9k_ipsec_la_ops.h  |  90 ++++
 drivers/crypto/cnxk/cnxk_cryptodev.c     |   6 +-
 drivers/crypto/cnxk/cnxk_cryptodev_ops.c |   2 +-
 drivers/crypto/cnxk/cnxk_cryptodev_ops.h |   1 +
 drivers/crypto/cnxk/meson.build          |   1 +
 14 files changed, 1006 insertions(+), 18 deletions(-)
 create mode 100644 drivers/crypto/cnxk/cn9k_ipsec.c
 create mode 100644 drivers/crypto/cnxk/cn9k_ipsec.h
 create mode 100644 drivers/crypto/cnxk/cn9k_ipsec_la_ops.h

-- 
2.22.0


             reply	other threads:[~2021-09-02 13:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 13:42 Archana Muniganti [this message]
2021-09-02 13:42 ` [dpdk-dev] [PATCH 1/8] crypto/cnxk: add cn9k security ctx Archana Muniganti
2021-09-02 13:42 ` [dpdk-dev] [PATCH 2/8] common/cnxk: add cn9k IPsec microcode defines Archana Muniganti
2021-09-02 13:42 ` [dpdk-dev] [PATCH 3/8] crypto/cnxk: add cn9k IPsec session related functions Archana Muniganti
2021-09-06 19:39   ` Akhil Goyal
2021-09-02 13:42 ` [dpdk-dev] [PATCH 4/8] crypto/cnxk: add cn9k IPsec outbound session create function Archana Muniganti
2021-09-02 13:42 ` [dpdk-dev] [PATCH 5/8] crypto/cnxk: add cn9k IPsec inbound " Archana Muniganti
2021-09-02 13:42 ` [dpdk-dev] [PATCH 6/8] crypto/cnxk: add cn9k lookaside IPsec datapath Archana Muniganti
2021-09-02 13:42 ` [dpdk-dev] [PATCH 7/8] crypto/cnxk: update tailroom requirement Archana Muniganti
2021-09-02 13:42 ` [dpdk-dev] [PATCH 8/8] crypto/cnxk: update feature flag for cn9k lookaside IPsec Archana Muniganti

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=20210902134254.28373-1-marchana@marvell.com \
    --to=marchana@marvell.com \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=ktejasree@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).