public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Prathamesh Deshpande <prathameshdeshpande7@gmail.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	dledford@redhat.com, haggaie@mellanox.com
Subject: Re: [PATCH v10 2/2] IB/mlx5: Serialize force-enable state and preserve loopback accounting
Date: Wed, 15 Apr 2026 01:58:53 +0100	[thread overview]
Message-ID: <20260415005923.34808-1-prathameshdeshpande7@gmail.com> (raw)
In-Reply-To: <20260413144155.GI21470@unreal>

On Mon, Apr 13, 2026 at 05:41:55PM +0300, Leon Romanovsky wrote:
> On Sun, Apr 12, 2026 at 02:18:50AM +0100, Prathamesh Deshpande wrote:
> > force_enable is shared between MP bind/unbind flows and regular loopback
> > enable/disable flows. MP helpers updated force_enable without lb.mutex,
> > while regular paths read it under lb.mutex.
> 
> Yes, this is intentional. During device probing, a device cannot be treated as
> both MP and regular at the same time.

Hi Leon,

Thanks for the clarification. I've addressed this in v11 by dropping the 
MP-related locking changes to keep the intentional behavior unchanged. 
The updated series has been submitted as a fresh thread.

Thanks,
Prathamesh

      reply	other threads:[~2026-04-15  0:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-12  1:18 [PATCH v10 0/2] IB/mlx5: Fix loopback rollback and locking Prathamesh Deshpande
2026-04-12  1:18 ` [PATCH v10 1/2] IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier Prathamesh Deshpande
2026-04-12  1:18 ` [PATCH v10 2/2] IB/mlx5: Serialize force-enable state and preserve loopback accounting Prathamesh Deshpande
2026-04-13 14:41   ` Leon Romanovsky
2026-04-15  0:58     ` Prathamesh Deshpande [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=20260415005923.34808-1-prathameshdeshpande7@gmail.com \
    --to=prathameshdeshpande7@gmail.com \
    --cc=dledford@redhat.com \
    --cc=haggaie@mellanox.com \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /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