From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Dooley, Brian" <brian.dooley@intel.com>, "Ji, Kai" <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"wathsala.vithanage@arm.com" <wathsala.vithanage@arm.com>
Subject: RE: [PATCH v1 1/1] crypto/ipsec_mb: unify some IPsec MB PMDs
Date: Thu, 20 Jun 2024 06:53:24 +0000 [thread overview]
Message-ID: <DM8PR11MB5591475EDC4C38BE3DCC13DD84C82@DM8PR11MB5591.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240605085346.272837-2-brian.dooley@intel.com>
> -----Original Message-----
> From: Dooley, Brian <brian.dooley@intel.com>
> Sent: Wednesday, June 5, 2024 10:54 AM
> To: Ji, Kai <kai.ji@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; gakhil@marvell.com; wathsala.vithanage@arm.com;
> Dooley, Brian <brian.dooley@intel.com>
> Subject: [PATCH v1 1/1] crypto/ipsec_mb: unify some IPsec MB PMDs
>
> 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>
> ---
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2024-06-20 6:53 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 ` [EXTERNAL] " Akhil Goyal
2024-06-20 6:53 ` De Lara Guarch, Pablo [this message]
2024-06-20 7:00 ` [PATCH v1 " 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=DM8PR11MB5591475EDC4C38BE3DCC13DD84C82@DM8PR11MB5591.namprd11.prod.outlook.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@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).