DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Maxime Leroy <maxime@leroys.fr>, hemant.agrawal@nxp.com
Cc: dev@dpdk.org, Sachin Saxena <sachin.saxena@nxp.com>
Subject: Re: [PATCH 4/5] net/dpaa2: remove ethdev device in bus device
Date: Wed, 12 Nov 2025 10:04:44 +0100	[thread overview]
Message-ID: <CAJFAV8ymqLUS_g4jH+pWVuSrMoF5LfNt001KYreVd50rfjUK=g@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8x4+2pwC=_NGM7J5ikyCY2tLAaQhS2uHLTG-_mShPAHEg@mail.gmail.com>

On Wed, 12 Nov 2025 at 09:56, David Marchand <david.marchand@redhat.com> wrote:
> On Wed, 12 Nov 2025 at 09:44, Maxime Leroy <maxime@leroys.fr> wrote:
> > 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.
>
> Indeed, moving the dpaa2_tx_sg_pool handling in dev_init/dev_close is
> more self contained, and looks cleaner.

On this topic, in rte_dpaa2_probe:

    /* Invoke PMD device initialization function */
    diag = dpaa2_dev_init(eth_dev);
    if (!diag) {
        diag = dpaa2_tx_sg_pool_init();
        if (diag)
            return diag;

On dpaa2_tx_sg_pool_init() failure, a eth_dev is leaked.
Worth fixing while moving around the code related to dpaa2_tx_sg_pool.


-- 
David Marchand


  reply	other threads:[~2025-11-12  9:05 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
2025-11-12  8:56     ` David Marchand
2025-11-12  9:04       ` David Marchand [this message]
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='CAJFAV8ymqLUS_g4jH+pWVuSrMoF5LfNt001KYreVd50rfjUK=g@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=maxime@leroys.fr \
    --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).