From: Raslan Darawsheh <rasland@nvidia.com>
To: Gavin Hu <gahu@nvidia.com>, dev@dpdk.org
Cc: Wei Yan <yanwei.wy@bytedance.com>,
stable@dpdk.org, 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>, Ophir Munk <ophirmu@nvidia.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Subject: Re: [PATCH v2] net/mlx5: avoid wildcard drop flow in priority discovery
Date: Mon, 3 Aug 2026 12:18:21 +0300 [thread overview]
Message-ID: <b62fba61-0317-485a-bb1e-e42cf271ff92@nvidia.com> (raw)
In-Reply-To: <20260714060751.44814-1-gahu@nvidia.com>
Hi,
On 14/07/2026 9:07 AM, Gavin Hu wrote:
> From: Wei Yan <yanwei.wy@bytedance.com>
>
> Priority discovery installs temporary drop flows to probe supported flow
> priorities. These flows match a wildcard Ethernet pattern, so they can
> also match real traffic while discovery is running. On shared devices this
> may temporarily drop kernel traffic and cause TCP connection timeouts.
>
> Constrain the probe flows to match both source and destination MAC
> addresses as ff:ff:ff:ff:ff:ff. This keeps the rule valid for discovery
> while avoiding matches on normal Ethernet traffic.
>
> Fixes: 3eca5f8a610e ("net/mlx5: move flow priority discovery to Verbs file")
> Fixes: c5042f93a425 ("net/mlx5: discover max flow priority using DevX")
> Cc: stable@dpdk.org
>
> Signed-off-by: Wei Yan <yanwei.wy@bytedance.com>
> Signed-off-by: Gavin Hu <gahu@nvidia.com>
> ---
> +v2:
> +* Fixed the compiling issue by some compilers in mlx5_flow_verbs.c.
>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2026-08-03 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 4:18 [PATCH] net/mlx5: avoid wildcard drop flow in priority discovery Gavin Hu
2026-07-13 10:56 ` Thomas Monjalon
2026-07-14 6:07 ` [PATCH v2] " Gavin Hu
2026-07-20 5:42 ` Suanming Mou
2026-08-03 9:18 ` 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=b62fba61-0317-485a-bb1e-e42cf271ff92@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dsosnowski@nvidia.com \
--cc=gahu@nvidia.com \
--cc=matan@nvidia.com \
--cc=ophirmu@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.com \
--cc=yanwei.wy@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.