DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tejasree Kondoj <ktejasree@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
	Nithinsen Kaithakadan <nkaithakadan@marvell.com>,
	Rupesh Chiluka <rchiluka@marvell.com>,
	"Vidya Sagar Velumuri" <vvelumuri@marvell.com>, <dev@dpdk.org>
Subject: [PATCH 0/9] fixes and new features to cnxk crypto PMD
Date: Tue, 27 May 2025 18:31:26 +0530	[thread overview]
Message-ID: <20250527130135.2301726-1-ktejasree@marvell.com> (raw)

This series adds fixes and new features to cnxk crypto PMD.
It is dependent on below series:
https://patches.dpdk.org/project/dpdk/list/?series=35294

Nithinsen Kaithakadan (4):
  common/cnxk: fix salt handling with aes-ctr
  common/cnxk: set correct salt value for ctr algos
  common/cnxk: update qsize in CPT iq enable
  crypto/cnxk: copy 8B iv into sess in aes ctr

Rupesh Chiluka (2):
  crypto/cnxk: extend check for max supported gather entries
  crypto/cnxk: add asym sessionless handling

Tejasree Kondoj (2):
  crypto/cnxk: include required headers
  crypto/cnxk: add struct variable for custom metadata

Vidya Sagar Velumuri (1):
  crypto/cnxk: add support for sessionless asym

 drivers/common/cnxk/cnxk_security.c       |  8 ++
 drivers/common/cnxk/roc_cpt.c             |  5 ++
 drivers/common/cnxk/roc_cpt_sg.h          |  1 +
 drivers/crypto/cnxk/cn10k_cryptodev_ops.c | 91 +++++++++++++++++++++--
 drivers/crypto/cnxk/cn10k_ipsec_la_ops.h  | 17 ++++-
 drivers/crypto/cnxk/cn10k_tls_ops.h       | 10 +++
 drivers/crypto/cnxk/cn20k_ipsec_la_ops.h  | 17 ++++-
 drivers/crypto/cnxk/cn20k_tls_ops.h       | 10 +++
 drivers/crypto/cnxk/cn9k_cryptodev_ops.c  | 77 ++++++++++++++++++-
 drivers/crypto/cnxk/cn9k_ipsec_la_ops.h   | 10 +++
 drivers/crypto/cnxk/cnxk_cryptodev.c      |  3 +-
 drivers/crypto/cnxk/cnxk_cryptodev_ops.c  |  5 +-
 drivers/crypto/cnxk/cnxk_cryptodev_ops.h  |  4 +
 drivers/crypto/cnxk/rte_pmd_cnxk_crypto.h |  3 +
 14 files changed, 244 insertions(+), 17 deletions(-)

-- 
2.25.1


             reply	other threads:[~2025-05-27 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 13:01 Tejasree Kondoj [this message]
2025-05-27 13:01 ` [PATCH 1/9] crypto/cnxk: include required headers Tejasree Kondoj
2025-05-27 13:01 ` [PATCH 2/9] common/cnxk: fix salt handling with aes-ctr Tejasree Kondoj
2025-05-27 13:01 ` [PATCH 3/9] common/cnxk: set correct salt value for ctr algos Tejasree Kondoj
2025-05-27 13:01 ` [PATCH 4/9] crypto/cnxk: extend check for max supported gather entries Tejasree Kondoj
2025-05-27 13:01 ` [PATCH 5/9] crypto/cnxk: add struct variable for custom metadata Tejasree Kondoj
2025-05-27 13:01 ` [PATCH 6/9] crypto/cnxk: add asym sessionless handling Tejasree Kondoj
2025-05-27 13:01 ` [PATCH 7/9] crypto/cnxk: add support for sessionless asym Tejasree Kondoj
2025-05-27 13:01 ` [PATCH 8/9] common/cnxk: update qsize in CPT iq enable Tejasree Kondoj
2025-05-27 13:01 ` [PATCH 9/9] crypto/cnxk: copy 8B iv into sess in aes ctr 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=20250527130135.2301726-1-ktejasree@marvell.com \
    --to=ktejasree@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=nkaithakadan@marvell.com \
    --cc=rchiluka@marvell.com \
    --cc=vvelumuri@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).