DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Andrew Boyer <andrew.boyer@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH 0/6] crypto/ionic: introduce AMD Pensando ionic crypto driver
Date: Wed, 24 Apr 2024 18:21:54 +0000	[thread overview]
Message-ID: <CO6PR18MB4484906AF846EF98955E30E5D8102@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240419195310.21432-1-andrew.boyer@amd.com>

Hi Andrew,
> 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.
> 
> Andrew Boyer (6):
>   crypto/ionic: introduce AMD Pensando ionic crypto driver
>   crypto/ionic: add device and admin command handlers
>   common/ionic: add crypto vdev support
>   crypto/ionic: add device object and vdev support
>   crypto/ionic: add datapath and capabilities support
>   crypto/ionic: add documentation and connect to build
I did not review the patches completely yet,
but the patches are not organized properly.

Your 1st patch says introduce the new driver, 
But it is just adding a hardware specific header file.

Your 1st patch should add the base framework of the PMD
Which is compiled in the DPDK build system.
You can also add some part of documentation for introducing the new driver.
MAINTAINERS file should also be updated for every new directory where it is introduced.

Once you have the base probe and remove added in your first patch,
You can add each of the driver ops in subsequent patches.
You can break queue pair related stuff in a single patch and session related stuff in another one.
Capabilities can be a separate patch.
enqueue/dequeue can also be separate patches as well if they are big.

Add documentation changes in each of the patches wherever needed.
You may refer https://patches.dpdk.org/project/dpdk/list/?series=17483&state=%2A&archive=both

> 
>  MAINTAINERS                              |    7 +
>  doc/guides/cryptodevs/features/ionic.ini |   40 +
>  doc/guides/cryptodevs/index.rst          |    1 +
>  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      |  361 ++++++++
>  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 |  993 +++++++++++++++++++++
>  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 +
>  16 files changed, 3969 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


  parent reply	other threads:[~2024-04-24 18:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 19:53 Andrew Boyer
2024-04-19 19:53 ` [PATCH 1/6] " Andrew Boyer
2024-04-19 19:53 ` [PATCH 2/6] crypto/ionic: add device and admin command handlers Andrew Boyer
2024-04-22 12:29   ` Boyer, Andrew
2024-04-19 19:53 ` [PATCH 3/6] common/ionic: add crypto vdev support Andrew Boyer
2024-04-19 19:53 ` [PATCH 4/6] crypto/ionic: add device object and " Andrew Boyer
2024-04-19 19:53 ` [PATCH 5/6] crypto/ionic: add datapath and capabilities support Andrew Boyer
2024-04-19 19:53 ` [PATCH 6/6] crypto/ionic: add documentation and connect to build Andrew Boyer
2024-04-24 18:21 ` Akhil Goyal [this message]
2024-04-30 20:21 ` [PATCH v2 0/9] crypto/ionic: introduce AMD Pensando ionic crypto driver Andrew Boyer
2024-04-30 20:21   ` [PATCH v2 1/9] " Andrew Boyer
2024-04-30 20:21   ` [PATCH v2 2/9] crypto/ionic: add the firmware interface definition file Andrew Boyer
2024-04-30 20:21   ` [PATCH v2 3/9] crypto/ionic: add device commands Andrew Boyer
2024-04-30 20:21   ` [PATCH v2 4/9] crypto/ionic: add adminq command support Andrew Boyer
2024-04-30 20:21   ` [PATCH v2 5/9] crypto/ionic: add capabilities and basic ops Andrew Boyer
2024-04-30 20:21   ` [PATCH v2 6/9] crypto/ionic: add session support Andrew Boyer
2024-04-30 20:21   ` [PATCH v2 7/9] crypto/ionic: add datapath Andrew Boyer
2024-04-30 20:21   ` [PATCH v2 8/9] crypto/ionic: add a watchdog operation Andrew Boyer
2024-04-30 20:21   ` [PATCH v2 9/9] crypto/ionic: add stats support Andrew Boyer

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=CO6PR18MB4484906AF846EF98955E30E5D8102@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=andrew.boyer@amd.com \
    --cc=dev@dpdk.org \
    /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).