All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: "Håkon Bugge" <haakon.bugge@oracle.com>
Cc: Doug Ledford <dledford@redhat.com>,
	Leon Romanovsky <leon@kernel.org>,
	linux-rdma@vger.kernel.org, Mark Zhang <markzhang@nvidia.com>
Subject: Re: [PATCH for-next v2 0/2] Fix RMW to bit-fields and remove one superfluous ib_modify_qp
Date: Fri, 25 Jun 2021 10:52:05 -0300	[thread overview]
Message-ID: <20210625135205.GA2991332@nvidia.com> (raw)
In-Reply-To: <1624369197-24578-1-git-send-email-haakon.bugge@oracle.com>

On Tue, Jun 22, 2021 at 03:39:55PM +0200, Håkon Bugge wrote:
> This series removes one superfluous ib_modify_qp() when a connected QP
> is created through rdma_create_qp(). This commit removes a call to
> rdma_init_qp_attr() for connected QPs without holding the qp_mutex.
> 
> The second commit tightens the access to bit-fields and synchronizes
> the access to them by means of mutex exclusion.
> 
> v1 -> v2:
>    * Added mutex protection in cma_resolve_iboe_route() for
>      timeout/timeout_set in commit ("RDMA/cma: Protect RMW with
>      qp_mutex")
> 
> Håkon Bugge (2):
>   RDMA/cma: Remove unnecessary INIT->INIT transition
>   RDMA/cma: Protect RMW with qp_mutex

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2021-06-25 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 13:39 [PATCH for-next v2 0/2] Fix RMW to bit-fields and remove one superfluous ib_modify_qp Håkon Bugge
2021-06-22 13:39 ` [PATCH for-next v2 1/2] RDMA/cma: Remove unnecessary INIT->INIT transition Håkon Bugge
2021-06-22 13:39 ` [PATCH for-next v2 2/2] RDMA/cma: Protect RMW with qp_mutex Håkon Bugge
2021-06-25 13:52 ` 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=20210625135205.GA2991332@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=haakon.bugge@oracle.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=markzhang@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.