linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Doug Ledford <dledford@redhat.com>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-next v2 5/7] RDMA/cm: Send and receive ECE parameter over the wire
Date: Mon, 25 May 2020 21:02:30 +0300	[thread overview]
Message-ID: <20200525180230.GJ10591@unreal> (raw)
In-Reply-To: <20200525175812.GB24366@ziepe.ca>

On Mon, May 25, 2020 at 02:58:12PM -0300, Jason Gunthorpe wrote:
> On Mon, Apr 13, 2020 at 05:15:36PM +0300, Leon Romanovsky wrote:
> > @@ -2204,6 +2220,12 @@ static void cm_format_rep(struct cm_rep_msg *rep_msg,
> >  		IBA_SET(CM_REP_LOCAL_EE_CONTEXT_NUMBER, rep_msg, param->qp_num);
> >  	}
> >
> > +	IBA_SET(CM_REP_VENDOR_ID_L, rep_msg, param->ece.vendor_id & 0xFF);
> > +	IBA_SET(CM_REP_VENDOR_ID_M, rep_msg,
> > +		(param->ece.vendor_id >> 8) & 0xFF);
> > +	IBA_SET(CM_REP_VENDOR_ID_H, rep_msg,
> > +		(param->ece.vendor_id >> 16) & 0xFF);
>
> I'm pretty sure the & 0xFF isn't needed?

vendor_id is 32 bits, but IBTA spec uses only 24 bits. I preferred to
write it implicitly, but of course IBA_SET() will mask it properly.

>
> > diff --git a/drivers/infiniband/core/ucma.c b/drivers/infiniband/core/ucma.c
> > index ed2c17046ee1..b67cdd2ef187 100644
> > +++ b/drivers/infiniband/core/ucma.c
> > @@ -362,7 +362,6 @@ static int ucma_event_handler(struct rdma_cm_id *cm_id,
> >
> >  	uevent->resp.ece.vendor_id = event->ece.vendor_id;
> >  	uevent->resp.ece.attr_mod = event->ece.attr_mod;
> > -
> >  	if (event->event == RDMA_CM_EVENT_CONNECT_REQUEST) {
> >  		if (!ctx->backlog) {
> >  			ret = -ENOMEM;
>
> Extra hunk?

Right

>
> Jason

  reply	other threads:[~2020-05-25 18:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 14:15 [PATCH rdma-next v2 0/7] Add Enhanced Connection Established (ECE) Leon Romanovsky
2020-04-13 14:15 ` [PATCH rdma-next v2 1/7] RDMA/cm: Add Enhanced Connection Establishment (ECE) bits Leon Romanovsky
2020-04-13 14:15 ` [PATCH rdma-next v2 2/7] RDMA/uapi: Add ECE definitions to UCMA Leon Romanovsky
2020-04-13 14:15 ` [PATCH rdma-next v2 3/7] RDMA/ucma: Extend ucma_connect to receive ECE parameters Leon Romanovsky
2020-05-25 17:41   ` Jason Gunthorpe
2020-05-25 17:47     ` Leon Romanovsky
2020-05-25 18:15       ` Jason Gunthorpe
2020-05-25 18:23         ` Leon Romanovsky
2020-04-13 14:15 ` [PATCH rdma-next v2 4/7] RDMA/ucma: Deliver ECE parameters through UCMA events Leon Romanovsky
2020-04-13 14:15 ` [PATCH rdma-next v2 5/7] RDMA/cm: Send and receive ECE parameter over the wire Leon Romanovsky
2020-05-25 17:58   ` Jason Gunthorpe
2020-05-25 18:02     ` Leon Romanovsky [this message]
2020-04-13 14:15 ` [PATCH rdma-next v2 6/7] RDMA/cma: Connect ECE to rdma_accept Leon Romanovsky
2020-04-13 14:15 ` [PATCH rdma-next v2 7/7] RDMA/cma: Provide ECE reject reason Leon Romanovsky
2020-05-25 18:14   ` Jason Gunthorpe
2020-05-25 18:22     ` Leon Romanovsky
2020-05-25 18:36       ` Jason Gunthorpe
2020-05-26  5:49         ` Leon Romanovsky
2020-04-20 13:36 ` [PATCH rdma-next v2 0/7] Add Enhanced Connection Established (ECE) Leon Romanovsky

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=20200525180230.GJ10591@unreal \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --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;
as well as URLs for NNTP newsgroup(s).