From: Or Har-Toov <ohartoov@nvidia.com>
To: Paolo Abeni <pabeni@redhat.com>, Tariq Toukan <tariqt@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org
Cc: Edward Srouji <edwards@nvidia.com>, Gal Pressman <gal@nvidia.com>,
Kees Cook <kees@kernel.org>, Leon Romanovsky <leon@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-rdma@vger.kernel.org, Maher Sanalla <msanalla@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>, Moshe Shemesh <moshe@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>, Shay Drori <shayd@nvidia.com>
Subject: Re: [PATCH net V2] net/mlx5: Lag, reset vport speed on MPESW teardown
Date: Sun, 25 Oct 2026 16:22:58 +0200 [thread overview]
Message-ID: <16368a7c-af34-4dfd-9e8c-891d455d2935@nvidia.com> (raw)
In-Reply-To: <4758dc6b-001c-4106-9258-f7d902fb01c7@redhat.com>
On 13/10/2026 14:33, Paolo Abeni wrote:
>
>
> On 10/6/26 13:24, Tariq Toukan wrote:
>> From: Or Har-Toov <ohartoov@nvidia.com>
>>
>> mlx5_lag_disable_mpesw() never called mlx5_lag_reset_vports_speed(),
>> unlike regular LAG teardown in mlx5_do_bond(), leaving stale cached and
>> FW-configured speeds after MPESW is torn down.
>>
>> Call it from mlx5_lag_disable_mpesw() as well, so the reset is paired
>> with mlx5_lag_set_vports_agg_speed() on the MPESW path too.
>>
>> Fixes: 50f1d188c580 ("net/mlx5: Propagate LAG effective max_tx_speed
>> to vports")
>> 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>
> The AI reported feedback looks like a pre-existing problem with
> mlx5_lag_reset_vports_speed(), but AFAICS it makes also the fix
> (partially) ineffective. I think this late in the cycle it's
> preferable to avoid partial fixes.
>
> /P
Hi, patch "Lag, save and restore vport max_tx_speed across LAG"
(https://lore.kernel.org/all/sashiko-outbox-183123@kernel.org/) that we
also send now it completing this fix.
prev parent reply other threads:[~2026-10-25 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 11:24 Tariq Toukan
2026-10-06 11:29 ` netdev-bot+sinfo
2026-10-07 12:28 ` Or Har-Toov
2026-10-08 11:25 ` netdev-bot+sashiko
2026-10-13 11:33 ` Paolo Abeni
2026-10-25 14:22 ` Or Har-Toov [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=16368a7c-af34-4dfd-9e8c-891d455d2935@nvidia.com \
--to=ohartoov@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=edwards@nvidia.com \
--cc=gal@nvidia.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=msanalla@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--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
all inboxes | Powered by JetHome®