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>
Subject: Re: [PATCH 4/5] net/dpaa2: remove ethdev device in bus device
Date: Wed, 12 Nov 2025 09:44:14 +0100 [thread overview]
Message-ID: <CAHHRULVe39Hq3ebQJVMfSfBMppEgZX0gmdzSqGoXNJWK5QtGGg@mail.gmail.com> (raw)
In-Reply-To: <20251108153207.1512863-5-david.marchand@redhat.com>
Hi David,
Le sam. 8 nov. 2025 à 16:32, David Marchand
<david.marchand@redhat.com> a écrit :
>
> Calling rte_eth_dev_allocated() is enough to retrieve the
> ethdev device object.
>
> This leaves no user of the ethdev field in the fslmc device object.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> drivers/bus/fslmc/bus_fslmc_driver.h | 1 -
> drivers/net/dpaa2/dpaa2_ethdev.c | 6 ++++--
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/bus/fslmc/bus_fslmc_driver.h b/drivers/bus/fslmc/bus_fslmc_driver.h
> index efa88754a7..094f885f59 100644
> --- a/drivers/bus/fslmc/bus_fslmc_driver.h
> +++ b/drivers/bus/fslmc/bus_fslmc_driver.h
> @@ -98,7 +98,6 @@ struct rte_dpaa2_device {
> TAILQ_ENTRY(rte_dpaa2_device) next; /**< Next probed DPAA2 device. */
> struct rte_device device; /**< Inherit core device */
> union {
> - struct rte_eth_dev *eth_dev; /**< ethernet device */
> struct rte_rawdev *rawdev; /**< Raw Device */
> };
> enum rte_dpaa2_dev_type dev_type; /**< Device Type */
> diff --git a/drivers/net/dpaa2/dpaa2_ethdev.c b/drivers/net/dpaa2/dpaa2_ethdev.c
> index 7da32ce856..2a26a02cb4 100644
> --- a/drivers/net/dpaa2/dpaa2_ethdev.c
> +++ b/drivers/net/dpaa2/dpaa2_ethdev.c
> @@ -3320,7 +3320,6 @@ rte_dpaa2_probe(struct rte_dpaa2_driver *dpaa2_drv,
>
> eth_dev->device = &dpaa2_dev->device;
>
> - dpaa2_dev->eth_dev = eth_dev;
> eth_dev->data->rx_mbuf_alloc_failed = 0;
>
> if (dpaa2_drv->drv_flags & RTE_DPAA2_DRV_INTR_LSC)
> @@ -3349,7 +3348,10 @@ rte_dpaa2_remove(struct rte_dpaa2_device *dpaa2_dev)
> struct rte_eth_dev *eth_dev;
> int ret;
>
> - eth_dev = dpaa2_dev->eth_dev;
> + eth_dev = rte_eth_dev_allocated(dpaa2_dev->device.name);
> + if (!eth_dev)
> + return 0;
> +
> dpaa2_dev_close(eth_dev);
> dpaa2_valid_dev--;
> if (!dpaa2_valid_dev)
dpaa2_valid_dev is currently incremented in rte_dpaa2_probe. With your
modification, dpaa2_valid_dev will never be decremented in
rte_dpaa2_remove if rte_eth_dev_close has already been called.
As a consequence, dpaa2_tx_sg_pool will never be freed.
I don’t think dpaa2_tx_sg_pool should be freed in rte_dpaa2_remove; it
should be freed in dpaa2_dev_close instead.
For symmetry, dpaa2_tx_sg_pool should also be allocated directly in
dpaa2_dev_init.
Regards,
Maxime Leroy
next prev parent reply other threads:[~2025-11-12 8:48 UTC|newest]
Thread overview: 16+ 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 [this message]
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-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-12 9:10 ` [PATCH v2 5/5] bus/fslmc: remove raw " David Marchand
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=CAHHRULVe39Hq3ebQJVMfSfBMppEgZX0gmdzSqGoXNJWK5QtGGg@mail.gmail.com \
--to=maxime@leroys.fr \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).