DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, dev@dpdk.org
Cc: mkashani@nvidia.com, Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH] net/mlx5: fix storage handling of shared Rx queues
Date: Mon, 18 Aug 2025 09:32:47 +0300	[thread overview]
Message-ID: <26c4e50f-6b9e-4bd3-afaf-1ccf9523ea08@nvidia.com> (raw)
In-Reply-To: <20250731104138.61593-1-getelson@nvidia.com>

Hi,


On 31/07/2025 1:41 PM, Gregory Etelson wrote:
> The MLX5 PMD maintains 2 lists for Rx queues:
> - mlx5_priv::rxqsctrl - for non-shared and shared Rx queues
> - mlx5_dev_ctx_shared::shared_rxqs - for shared Rx queues only
> 
> The PMD used the `rxqsctrl` as the primary list for Rx queues
> maintenance.
> 
> The PMD wipes out port mlx5_priv object after an application closed
> the port.
> 
> If PMD shared Rx queues between the transfer proxy port and
> representor ports and closed the transfer proxy port before
> representor, the representor port cannot iterate its shared Rx queues
> because Rx queues list head was wiped out.
> 
> The patch separates Rx queue storage list according to the list type:
> - shared Rx queues are stored in the `shared_rxqs` only
> - non-shared Rx queues are stored in the `rxqsctrl` list only.
> 
> Fixes: 6886b5f39d66 ("net/mlx5: fix hairpin queue release")
> 
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh


      reply	other threads:[~2025-08-18  6:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 10:41 Gregory Etelson
2025-08-18  6:32 ` 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=26c4e50f-6b9e-4bd3-afaf-1ccf9523ea08@nvidia.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --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).