DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Brian Dooley <brian.dooley@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	"wathsala.vithanage@arm.com" <wathsala.vithanage@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Kai Ji <kai.ji@intel.com>
Subject: RE: [EXTERNAL] [PATCH v2 1/1] crypto/ipsec_mb: unify some IPsec MB PMDs
Date: Wed, 26 Jun 2024 08:26:16 +0000	[thread overview]
Message-ID: <CO6PR18MB448433F082B6FF8E80FE3555D8D62@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240614140759.1123505-2-brian.dooley@intel.com>

> Currently IPsec MB provides both the JOB API and direct API.
> AESNI_MB PMD is using the JOB API codepath while KASUMI and
> CHACHA20_POLY1305 are using the direct API.
> Instead of using the direct API for these PMDs, they should now make
> use of the JOB API codepath. This would remove all use of the IPsec MB
> direct API for these PMDs.
> 
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>

Applied to dpdk-next-crypto
Pablo's ack taken from v1.

Wathsala, I hope this is tested for ARM repo.

  reply	other threads:[~2024-06-26  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  8:53 [PATCH v1 0/1] Unifying IPsec MB Brian Dooley
2024-06-05  8:53 ` [PATCH v1 1/1] crypto/ipsec_mb: unify some IPsec MB PMDs Brian Dooley
2024-06-14 14:07   ` [PATCH v2 0/1] Unifying IPsec MB Brian Dooley
2024-06-14 14:07     ` [PATCH v2 1/1] crypto/ipsec_mb: unify some IPsec MB PMDs Brian Dooley
2024-06-26  8:26       ` Akhil Goyal [this message]
2024-06-20  6:53   ` [PATCH v1 " De Lara Guarch, Pablo
2024-06-20  7:00     ` Akhil Goyal

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=CO6PR18MB448433F082B6FF8E80FE3555D8D62@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=wathsala.vithanage@arm.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).