DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Anoob Joseph <anoobj@marvell.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Jerin Jacob <jerinj@marvell.com>,
	Narayana Prasad <pathreya@marvell.com>,
	Ankur Dwivedi <adwivedi@marvell.com>,
	 Tejasree Kondoj <ktejasree@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/6] improvements to OCTEON TX crypto PMDs
Date: Sun, 17 May 2020 14:16:11 +0000	[thread overview]
Message-ID: <VI1PR04MB3168E2CC1B0CD93EE88271EBE6BB0@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1589621218-25339-1-git-send-email-anoobj@marvell.com>

Hi Anoob,

This patch series is pretty late for the RC3, specially your last patch.
However the patches looks good to me, I have applied them to dpdk-next-crypto
with some modifications in the commit titles and descriptions.

Please send the fixes a bit earlier from next time.

Regards,
Akhil
> 
> This series adds multiple optimizations and improvements to OCTEON TX crypto
> PMDs
> and OCTEON TX2 security support.
> 
> Ankur Dwivedi (2):
>   crypto/octeontx2: enable non-byte aligned data feature
>   crypto/octeontx: enable non-byte aligned data feature
> 
> Anoob Joseph (3):
>   common/octeontx2: fix out of bounds access
>   crypto/octeontx2: improve error handling in session configure
>   crypto/octeontx: redesign sym sessionless code path
> 
> Tejasree Kondoj (1):
>   net/octeontx2: increase max packet length for Inline IPsec Rx
> 
>  doc/guides/cryptodevs/features/octeontx.ini   |   1 +
>  doc/guides/cryptodevs/features/octeontx2.ini  |   1 +
>  drivers/common/cpt/cpt_ucode.h                |  75 ---------
>  drivers/common/octeontx2/otx2_sec_idev.c      |   4 +-
>  drivers/crypto/octeontx/otx_cryptodev_ops.c   | 210 ++++++++++++++-----------
> -
>  drivers/crypto/octeontx2/otx2_cryptodev.c     |   1 +
>  drivers/crypto/octeontx2/otx2_cryptodev_ops.c |  43 +++++-
>  drivers/net/octeontx2/otx2_ethdev_sec.c       |   4 +-
>  8 files changed, 160 insertions(+), 179 deletions(-)
> 
> --
> 2.7.4


  parent reply	other threads:[~2020-05-17 14:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16  9:26 Anoob Joseph
2020-05-16  9:26 ` [dpdk-dev] [PATCH 1/6] common/octeontx2: fix out of bounds access Anoob Joseph
2020-05-16  9:26 ` [dpdk-dev] [PATCH 2/6] net/octeontx2: increase max packet length for Inline IPsec Rx Anoob Joseph
2020-05-16  9:26 ` [dpdk-dev] [PATCH 3/6] crypto/octeontx2: enable non-byte aligned data feature Anoob Joseph
2020-05-16  9:26 ` [dpdk-dev] [PATCH 4/6] crypto/octeontx2: improve error handling in session configure Anoob Joseph
2020-05-16  9:26 ` [dpdk-dev] [PATCH 5/6] crypto/octeontx: enable non-byte aligned data feature Anoob Joseph
2020-05-16  9:26 ` [dpdk-dev] [PATCH 6/6] crypto/octeontx: redesign sym sessionless code path Anoob Joseph
2020-05-17 14:16 ` Akhil Goyal [this message]
2020-05-18  4:26   ` [dpdk-dev] [PATCH 0/6] improvements to OCTEON TX crypto PMDs Anoob Joseph
  -- strict thread matches above, loose matches on Subject: below --
2020-05-16  9:20 Anoob Joseph

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=VI1PR04MB3168E2CC1B0CD93EE88271EBE6BB0@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=ktejasree@marvell.com \
    --cc=pathreya@marvell.com \
    --cc=thomas@monjalon.net \
    /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).