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
Subject: Re: [PATCH v2] net/mlx5: remove representor matching devarg
Date: Mon, 17 Nov 2025 09:43:56 +0200 [thread overview]
Message-ID: <d8f955f9-8536-49bf-906e-7018120c7cbc@nvidia.com> (raw)
In-Reply-To: <20251113131758.1524043-1-dsosnowski@nvidia.com>
Hi,
On 13/11/2025 3:17 PM, Dariusz Sosnowski wrote:
> As announced in 25.07 release deprecation notice [1],
> this patch removes repr_matching_en device argument from mlx5 driver.
>
> Applications which disabled this option were able to receive traffic
> from any physical port/VF/SF on any representor.
> Specifically, in most cases, this was used to process all traffic
> on representor which is a transfer proxy port.
> Similar behavior in mlx5 PMD can be achieved without
> the use of additional device arguments, by using
> RTE_FLOW_ACTION_TYPE_RSS flow action in transfer flow rules.
>
> [1] https://doc.dpdk.org/guides-25.07/rel_notes/deprecation.html
>
> 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:[~2025-11-17 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 19:35 [PATCH] " Dariusz Sosnowski
2025-11-06 7:31 ` Bing Zhao
2025-11-13 13:17 ` [PATCH v2] " Dariusz Sosnowski
2025-11-17 7:43 ` 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=d8f955f9-8536-49bf-906e-7018120c7cbc@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=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).