DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Archana Muniganti <marchana@marvell.com>
Cc: Archana Muniganti <marchana@marvell.com>,
	Tejasree Kondoj <ktejasree@marvell.com>,
	Ankur Dwivedi <adwivedi@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/6] add cn9k lookaside IPsec support
Date: Tue, 7 Sep 2021 18:22:55 +0000	[thread overview]
Message-ID: <PH0PR18MB449103753EFD1011C77340E5D8D39@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210907142103.18807-1-marchana@marvell.com>

> This series adds lookaside IPsec support in cnxk crypto PMD
> for Marvell CN9K SOC.
> 
> Changes in v2:
> - Fixed release notes
> - Squashed patches and reduced no of patches from 8 to 6
> 
> Archana Muniganti (6):
>   crypto/cnxk: add cn9k security ctx
>   common/cnxk: add cn9k IPsec microcode defines
>   crypto/cnxk: add cn9k security session ops
>   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   |   1 +
>  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         | 610 +++++++++++++++++++++++
>  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, 1002 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
> 
Applied to dpdk-next-crypto

Thanks.

      parent reply	other threads:[~2021-09-07 18:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 14:20 Archana Muniganti
2021-09-07 14:20 ` [dpdk-dev] [PATCH v2 1/6] crypto/cnxk: add cn9k security ctx Archana Muniganti
2021-09-07 14:20 ` [dpdk-dev] [PATCH v2 2/6] common/cnxk: add cn9k IPsec microcode defines Archana Muniganti
2021-09-07 14:21 ` [dpdk-dev] [PATCH v2 3/6] crypto/cnxk: add cn9k security session ops Archana Muniganti
2021-09-07 14:21 ` [dpdk-dev] [PATCH v2 4/6] crypto/cnxk: add cn9k lookaside IPsec datapath Archana Muniganti
2021-09-07 14:21 ` [dpdk-dev] [PATCH v2 5/6] crypto/cnxk: update tailroom requirement Archana Muniganti
2021-09-07 14:21 ` [dpdk-dev] [PATCH v2 6/6] crypto/cnxk: update feature flag for cn9k lookaside IPsec Archana Muniganti
2021-09-07 16:02 ` [dpdk-dev] [PATCH v2 0/6] add cn9k lookaside IPsec support Anoob Joseph
2021-09-07 18:22 ` Akhil Goyal [this message]

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=PH0PR18MB449103753EFD1011C77340E5D8D39@PH0PR18MB4491.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=ktejasree@marvell.com \
    --cc=marchana@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).