From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next] net/mlx5: E-Switch, Size FDB peer groups for asymmetric peers
Date: Mon, 16 Nov 2026 21:17:22 +0000 [thread overview]
Message-ID: <sashiko-outbox-217696@kernel.org> (raw)
In-Reply-To: <20261116210917.1297111-1-tariqt@nvidia.com>
> From: Uri Dar <udar@nvidia.com>
>
> The slow path FDB send-to-vport and peer-miss groups are sized from the
> local eswitch total_vports, assuming every eswitch that may pair has the
> same number of vports. Per-PF VF configuration (e.g. PF_NUM_OF_VF set
> differently per port) breaks that assumption: the larger peer installs
> rules sized by its own total_vports into the smaller peer's groups,
> which cannot hold them, so pairing fails.
>
> In SW and HW steering the flow table is unbounded (max_fte is INT_MAX)
> and flow groups are backed by dynamically grown matchers, so size the
> peer dependent groups to the architectural vport maximum. FW steering,
> whose table is bounded by log_max_ft_size, keeps the current sizing.
>
> Signed-off-by: Uri Dar <udar@nvidia.com>
> Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
> Reviewed-by: Shay Drori <shayd@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261116210917.1297111-1-tariqt@nvidia.com?part=1
prev parent reply other threads:[~2026-11-16 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 21:09 [PATCH net-next] net/mlx5: E-Switch, Size FDB peer groups for asymmetric peers Tariq Toukan
2026-11-16 21:17 ` sashiko-bot [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=sashiko-outbox-217696@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tariqt@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