From: Jason Gunthorpe <jgg@nvidia.com>
To: Prathamesh Deshpande <prathameshdeshpande7@gmail.com>
Cc: Leon Romanovsky <leon@kernel.org>,
Patrisious Haddad <phaddad@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>,
Doug Ledford <dledford@redhat.com>,
Haggai Eran <haggaie@nvidia.com>, Majd Dibbiny <majd@nvidia.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v12 2/2] IB/mlx5: Fix loopback threshold/accounting in regular path
Date: Fri, 5 Jun 2026 14:35:27 -0300 [thread overview]
Message-ID: <20260605173527.GA2786594@nvidia.com> (raw)
In-Reply-To: <20260510222258.6654-3-prathameshdeshpande7@gmail.com>
On Sun, May 10, 2026 at 11:22:54PM +0100, Prathamesh Deshpande wrote:
> In regular (non-MP) loopback enable/disable paths, threshold logic uses a
> hardcoded user_td baseline and does not rollback counters when HW enable
> fails.
This is two things again. I took the cleaner version of the rollback
fix from someone else.
I have no idea what this is supposed to mean:
> Use a TD-capability-aware baseline for user_td transitions, and rollback
> user_td/qps accounting if mlx5_nic_vport_update_local_lb() fails.
Jason
prev parent reply other threads:[~2026-06-05 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 22:22 [PATCH v12 0/2] IB/mlx5: Fix loopback rollback and threshold accounting Prathamesh Deshpande
2026-05-10 22:22 ` [PATCH v12 1/2] IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier Prathamesh Deshpande
2026-06-03 0:29 ` Jason Gunthorpe
2026-05-10 22:22 ` [PATCH v12 2/2] IB/mlx5: Fix loopback threshold/accounting in regular path Prathamesh Deshpande
2026-06-05 17:35 ` Jason Gunthorpe [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=20260605173527.GA2786594@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=haggaie@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=majd@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=phaddad@nvidia.com \
--cc=prathameshdeshpande7@gmail.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