From: Ciara Power <ciara.power@intel.com>
To: dev@dpdk.org
Cc: roy.fan.zhang@intel.com, kai.ji@intel.com,
Ciara Power <ciara.power@intel.com>
Subject: [PATCH 0/3] add partial SGL support to AESNI_MB
Date: Thu, 7 Apr 2022 10:30:38 +0000 [thread overview]
Message-ID: <20220407103041.4037942-1-ciara.power@intel.com> (raw)
This patchset adds SGL support for GCM and CHACHA20-POLY1305 algorithms,
using the IPSec-MB JOB API.
Supported SGL types:
- INPLACE SGL
- OOP SGL IN, LB OUT
- OOP SGL IN, SGL OUT
The SGL Feature Flags for AESNI_MB PMD are not added,
as it does not yet support SGL for all other algorithms.
Ciara Power (3):
crypto/ipsec_mb: add GCM sgl support to aesni_mb
crypto/ipsec_mb: add chachapoly SGL support to aesni_mb
crypto/ipsec_mb: check SGL support for algorithm
drivers/crypto/ipsec_mb/pmd_aesni_mb.c | 160 +++++++++++++++++++-
drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h | 5 +
2 files changed, 160 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2022-04-07 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 10:30 Ciara Power [this message]
2022-04-07 10:30 ` [PATCH 1/3] crypto/ipsec_mb: add GCM sgl support to aesni_mb Ciara Power
2022-05-08 14:39 ` De Lara Guarch, Pablo
2022-05-11 12:35 ` Power, Ciara
2022-04-07 10:30 ` [PATCH 2/3] crypto/ipsec_mb: add chachapoly SGL " Ciara Power
2022-04-07 10:30 ` [PATCH 3/3] crypto/ipsec_mb: check SGL support for algorithm Ciara Power
2022-05-08 14:39 ` De Lara Guarch, Pablo
2022-05-02 9:48 ` [EXT] [PATCH 0/3] add partial SGL support to AESNI_MB Akhil Goyal
2022-05-05 14:47 ` De Lara Guarch, Pablo
2022-05-11 12:30 ` [PATCH v2 0/2] " Ciara Power
2022-05-11 12:30 ` [PATCH v2 1/2] crypto/ipsec_mb: add GCM SGL support to aesni-mb Ciara Power
2022-05-11 12:30 ` [PATCH v2 2/2] crypto/ipsec_mb: add chachapoly " Ciara Power
2022-05-11 15:44 ` [PATCH v2 0/2] add partial SGL support to AESNI_MB De Lara Guarch, Pablo
2022-05-26 16:13 ` [EXT] " 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=20220407103041.4037942-1-ciara.power@intel.com \
--to=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=roy.fan.zhang@intel.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).