From: "Boyer, Andrew" <Andrew.Boyer@amd.com>
To: Akhil Goyal <gakhil@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [RFC 0/5] crypto/ionic: introduce AMD Pensando ionic crypto driver
Date: Fri, 1 Mar 2024 13:23:38 +0000 [thread overview]
Message-ID: <39810723-07E3-4A39-BA5F-E512C75D7DF2@amd.com> (raw)
In-Reply-To: <20240222184019.15301-1-andrew.boyer@amd.com>
> On Feb 22, 2024, at 1:40 PM, Boyer, Andrew <Andrew.Boyer@amd.com> wrote:
>
> This patchset introduces a new crypto PMD for AMD Pensando hardware
> accelerators. It allows applications running directly on the AMD Pensando
> DSC to offload cryptographic operations to hardware cryptographic blocks.
>
> Depends-on: series-31157 ("net/ionic, common/ionic: add vdev support")
>
> Andrew Boyer (5):
> crypto/ionic: introduce AMD Pensando ionic crypto driver
> crypto/ionic: add device and admin command handlers
> crypto/ionic: add device object and vdev support
> crypto/ionic: add datapath and capabilities support
> crypto/ionic: add documentation
>
> MAINTAINERS | 7 +
> doc/guides/cryptodevs/features/ionic.ini | 40 +
> doc/guides/cryptodevs/ionic.rst | 39 +
> drivers/common/ionic/ionic_common.h | 2 +
> drivers/common/ionic/ionic_common_uio.c | 48 +-
> drivers/common/ionic/version.map | 1 +
> drivers/crypto/ionic/ionic_crypto.h | 360 ++++++++
> drivers/crypto/ionic/ionic_crypto_caps.c | 55 ++
> drivers/crypto/ionic/ionic_crypto_cmds.c | 651 ++++++++++++++
> drivers/crypto/ionic/ionic_crypto_if.h | 1021 ++++++++++++++++++++++
> drivers/crypto/ionic/ionic_crypto_main.c | 991 +++++++++++++++++++++
> drivers/crypto/ionic/ionic_crypto_ops.c | 606 +++++++++++++
> drivers/crypto/ionic/ionic_crypto_vdev.c | 128 +++
> drivers/crypto/ionic/meson.build | 16 +
> drivers/crypto/meson.build | 1 +
> 15 files changed, 3965 insertions(+), 1 deletion(-)
> create mode 100644 doc/guides/cryptodevs/features/ionic.ini
> create mode 100644 doc/guides/cryptodevs/ionic.rst
> create mode 100644 drivers/crypto/ionic/ionic_crypto.h
> create mode 100644 drivers/crypto/ionic/ionic_crypto_caps.c
> create mode 100644 drivers/crypto/ionic/ionic_crypto_cmds.c
> create mode 100644 drivers/crypto/ionic/ionic_crypto_if.h
> create mode 100644 drivers/crypto/ionic/ionic_crypto_main.c
> create mode 100644 drivers/crypto/ionic/ionic_crypto_ops.c
> create mode 100644 drivers/crypto/ionic/ionic_crypto_vdev.c
> create mode 100644 drivers/crypto/ionic/meson.build
>
> --
> 2.17.1
>
Akhil,
Are you deferring this out of the upcoming release?
-Andrew
next prev parent reply other threads:[~2024-03-01 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 18:40 Andrew Boyer
2024-02-22 18:40 ` [RFC 1/5] " Andrew Boyer
2024-02-22 18:40 ` [RFC 2/5] crypto/ionic: add device and admin command handlers Andrew Boyer
2024-02-22 18:40 ` [RFC 3/5] crypto/ionic: add device object and vdev support Andrew Boyer
2024-02-22 18:40 ` [RFC 4/5] crypto/ionic: add datapath and capabilities support Andrew Boyer
2024-02-22 18:40 ` [RFC 5/5] crypto/ionic: add documentation Andrew Boyer
2024-03-01 13:23 ` Boyer, Andrew [this message]
2024-03-01 13:27 ` [RFC 0/5] crypto/ionic: introduce AMD Pensando ionic crypto driver 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=39810723-07E3-4A39-BA5F-E512C75D7DF2@amd.com \
--to=andrew.boyer@amd.com \
--cc=dev@dpdk.org \
--cc=gakhil@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).