DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Leroy <maxime@leroys.fr>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, hemant.agrawal@nxp.com,
	 Sachin Saxena <sachin.saxena@nxp.com>,
	Gagandeep Singh <g.singh@nxp.com>
Subject: Re: [PATCH v2 1/5] crypto/dpaa2_sec: remove crypto device in bus device
Date: Mon, 17 Nov 2025 09:35:59 +0100	[thread overview]
Message-ID: <CAHHRULXYKbmYT7tY4Qino9dhZccZwBoQYJusjDNJkOi6e62NHw@mail.gmail.com> (raw)
In-Reply-To: <20251112091049.2669481-2-david.marchand@redhat.com>

Hi David,

Le mer. 12 nov. 2025 à 10:11, David Marchand
<david.marchand@redhat.com> a écrit :
>
> Calling rte_cryptodev_pmd_get_named_dev() is enough to retrieve the
> crypto device object.
>
> This leaves no user of the cryptodev field in the fslmc device object.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>  drivers/bus/fslmc/bus_fslmc_driver.h        | 1 -
>  drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 8 +++++---
>  2 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/bus/fslmc/bus_fslmc_driver.h b/drivers/bus/fslmc/bus_fslmc_driver.h
> index b6a6238a01..45c7a519f9 100644
> --- a/drivers/bus/fslmc/bus_fslmc_driver.h
> +++ b/drivers/bus/fslmc/bus_fslmc_driver.h
> @@ -99,7 +99,6 @@ struct rte_dpaa2_device {
>         struct rte_device device;           /**< Inherit core device */
>         union {
>                 struct rte_eth_dev *eth_dev;        /**< ethernet device */
> -               struct rte_cryptodev *cryptodev;    /**< Crypto Device */
>                 struct rte_dma_dev *dmadev;          /**< DMA Device */
>                 struct rte_rawdev *rawdev;          /**< Raw Device */
>         };
> diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
> index ca10d88da7..698548e6ea 100644
> --- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
> +++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
> @@ -4503,8 +4503,6 @@ cryptodev_dpaa2_sec_probe(struct rte_dpaa2_driver *dpaa2_drv __rte_unused,
>                 return -ENOMEM;
>         }
>
> -       dpaa2_dev->cryptodev = cryptodev;
> -
>         if (dpaa2_svr_family == SVR_LX2160A)
>                 rta_set_sec_era(RTA_SEC_ERA_10);
>         else
> @@ -4526,10 +4524,14 @@ cryptodev_dpaa2_sec_probe(struct rte_dpaa2_driver *dpaa2_drv __rte_unused,
>  static int
>  cryptodev_dpaa2_sec_remove(struct rte_dpaa2_device *dpaa2_dev)
>  {
> +       char cryptodev_name[RTE_CRYPTODEV_NAME_MAX_LEN];
>         struct rte_cryptodev *cryptodev;
>         int ret;
>
> -       cryptodev = dpaa2_dev->cryptodev;
> +       snprintf(cryptodev_name, sizeof(cryptodev_name), "dpsec-%d",
> +                       dpaa2_dev->object_id);
> +
> +       cryptodev = rte_cryptodev_pmd_get_named_dev(cryptodev_name);
>         if (cryptodev == NULL)
>                 return -ENODEV;
>
> --
> 2.51.0
>
Should we add a function to generate the cryptodev name instead of
duplicating the code, similar to how it’s done for PCI devices (i.e.,
rte_pci_device_name)?

Maxime Leroy

  reply	other threads:[~2025-11-17  8:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-08 15:32 [PATCH 0/5] Cleanup rte_dpaa2_device David Marchand
2025-11-08 15:32 ` [PATCH 1/5] crypto/dpaa2_sec: remove crypto device in bus device David Marchand
2025-11-08 15:32 ` [PATCH 2/5] dma/dpaa2: remove DMA " David Marchand
2025-11-08 15:32 ` [PATCH 3/5] net/dpaa2: remove dead code in loopback mode David Marchand
2025-11-08 15:32 ` [PATCH 4/5] net/dpaa2: remove ethdev device in bus device David Marchand
2025-11-12  8:44   ` Maxime Leroy
2025-11-12  8:56     ` David Marchand
2025-11-12  9:04       ` David Marchand
2025-11-08 15:32 ` [PATCH 5/5] bus/fslmc: remove raw " David Marchand
2025-11-12  7:35 ` [PATCH 0/5] Cleanup rte_dpaa2_device Hemant Agrawal
2025-11-12  9:10 ` [PATCH v2 " David Marchand
2025-11-12  9:10   ` [PATCH v2 1/5] crypto/dpaa2_sec: remove crypto device in bus device David Marchand
2025-11-17  8:35     ` Maxime Leroy [this message]
2025-11-17  8:58       ` David Marchand
2025-11-17  9:28         ` Maxime Leroy
2025-11-12  9:10   ` [PATCH v2 2/5] dma/dpaa2: remove DMA " David Marchand
2025-11-12  9:10   ` [PATCH v2 3/5] net/dpaa2: remove dead code in loopback mode David Marchand
2025-11-12  9:10   ` [PATCH v2 4/5] net/dpaa2: remove ethdev device in bus device David Marchand
2025-11-13  9:15     ` Hemant Agrawal
2025-11-12  9:10   ` [PATCH v2 5/5] bus/fslmc: remove raw " David Marchand
2025-11-13  9:16   ` [PATCH v2 0/5] Cleanup rte_dpaa2_device Hemant Agrawal

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=CAHHRULXYKbmYT7tY4Qino9dhZccZwBoQYJusjDNJkOi6e62NHw@mail.gmail.com \
    --to=maxime@leroys.fr \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=sachin.saxena@nxp.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).