DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Bing Zhao <bingz@nvidia.com>, viacheslavo@nvidia.com, dev@dpdk.org
Cc: orika@nvidia.com, dsosnowski@nvidia.com, suanmingm@nvidia.com,
	matan@nvidia.com, thomas@monjalon.net
Subject: Re: [PATCH] net/mlx5: fix decreasing the reference count of a Tx queue
Date: Sun, 6 Jul 2025 17:17:16 +0300	[thread overview]
Message-ID: <e5fb3ee0-5e42-46b8-96d6-5f094a620939@nvidia.com> (raw)
In-Reply-To: <20250703150252.145065-1-bingz@nvidia.com>

Hi,


On 03/07/2025 6:02 PM, Bing Zhao wrote:
> When changing the order of the Tx queues startup, the depth of the
> queue is compared. If not equal to the current big log2 value, next
> queue will be checked and the current one will be skipped for the
> next iteration.
> 
> The mlx5_txq_get() will increase the reference count number, and the
> size check no match is not an error and the startup will continue but
> not fall into the error roll-back label. The reference count should
> be decreased by 1 to dereference the count, or else in the device
> close stage, the queue cannot be released in the FW and the TIS, PD
> will be leaked as well.
> 
> By calling the mlx5_txq_release() before continue will recover the
> reference count to the initial state and solve the leak.
> 
> Fixes: 6f356d3840e6 ("net/mlx5: pass DevX object info in Tx queue start")
> 
> Signed-off-by: Bing Zhao <bingz@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh


      reply	other threads:[~2025-07-06 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 15:02 Bing Zhao
2025-07-06 14:17 ` Raslan Darawsheh [this message]

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=e5fb3ee0-5e42-46b8-96d6-5f094a620939@nvidia.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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).