From: Raslan Darawsheh <rasland@nvidia.com>
To: 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>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5: fix skipping PF representors
Date: Thu, 9 Apr 2026 11:40:40 +0300 [thread overview]
Message-ID: <d6c2aec1-21d5-4ec1-b969-3bb040a8db79@nvidia.com> (raw)
In-Reply-To: <20260407103130.142440-1-dsosnowski@nvidia.com>
Hi,
On 07/04/2026 1:31 PM, Dariusz Sosnowski wrote:
> Offending patch changed logic of matching IB ports to requested
> representors in mlx5 driver.
> Each found IB port was matched against all requested representors.
> Whenever:
>
> - requested representor was VF or SF
> - PF was not ignored
> - IB port was physical port
> - physical port index matched requested PF index
>
> the physical port representor was probed.
> If any of the above is false, mlx5 driver should have continue testing
> other requested PF representors.
> In the offending patch, the representor matching loop was stopped.
> As a result, if mlx5 device with MPESW enabled was probed with the
> following devargs:
>
> -a 08:00.0,dv_flow_en=2,representor=pf[0-1]vf[0,1]
>
> Only 5 ports were probed (physical port 0 and all VF representors),
> instead of 6 ports (physical port 1 is missing).
>
> This patch fixes that by continuing representor matching loop
> on physical port to PF index mismatch as described above.
>
> Fixes: 2f7cdd821b1b ("net/mlx5: fix probing to allow BlueField Socket Direct")
> Cc: stable@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Bing Zhao <bingz@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2026-04-09 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 10:31 [PATCH] net/mlx5: fix skipping PF representors Dariusz Sosnowski
2026-04-09 8:40 ` 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=d6c2aec1-21d5-4ec1-b969-3bb040a8db79@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=stable@dpdk.org \
--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