From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net V2] net/mlx5: Lag, split aggregate speed into oper and max helpers
Date: Wed, 30 Sep 2026 17:12:28 +0000 [thread overview]
Message-ID: <20260930171229.1E1871F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260930170406.148548-1-tariqt@nvidia.com>
> From: Or Har-Toov <ohartoov@nvidia.com>
>
> mlx5_lag_sum_devices_speed computes the LAG aggregate by summing oper
> speeds across all ports. This has two bugs.
>
> First, it relies on the assumption that a port whose carrier is down
> will report an oper speed of zero and therefore not contribute to the
> sum. This assumption does not always hold: when the link partner
> disconnects the port transitions to DOWN state but firmware may still
> report a non-zero oper speed, causing the aggregate to include a port
> that is not actively carrying traffic.
>
> Second, in active-backup mode only one port transmits at a time, so
> the aggregate should reflect a single port speed rather than the sum
> of all ports.
>
> Fix this by splitting mlx5_lag_sum_devices_speed into two helpers.
> mlx5_lag_get_devices_oper_speed reflects the speed currently available:
> it queries the vport state of each port and skips any port that is not
> UP, rather than relying on oper speed being zero.
> mlx5_lag_get_devices_max_speed is state-independent and returns the
> maximum achievable speed used as a fallback when speed is 0; for
> active-backup it takes the maximum single-port speed instead of the sum.
>
> Fixes: 28ea6036dad2 ("net/mlx5: Handle port and vport speed change events in MPESW")
> Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
> Reviewed-by: Shay Drori <shayd@nvidia.com>
> Reviewed-by: Mark Bloch <mbloch@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930170406.148548-1-tariqt@nvidia.com?part=1
next prev parent reply other threads:[~2026-09-30 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 17:04 [PATCH net V2] net/mlx5: Lag, split aggregate speed into oper and max helpers Tariq Toukan
2026-09-30 17:08 ` netdev-bot+sinfo
2026-10-05 15:44 ` Or Har-Toov
2026-09-30 17:12 ` sashiko-bot [this message]
2026-10-05 23:00 ` patchwork-bot+netdevbpf
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=20260930171229.1E1871F00898@smtp.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 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.