All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Kalderon <mkalderon@marvell.com>
To: Kamal Heib <kamalheib1@gmail.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: Ariel Elior <aelior@marvell.com>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: RE: [EXT] [PATCH for-next] RDMA/qedr: Fix reporting max_{send/recv}_wr attrs
Date: Tue, 7 Dec 2021 10:56:59 +0000	[thread overview]
Message-ID: <CH0PR18MB41292180806C1D1DF3E0DE58A16E9@CH0PR18MB4129.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20211206201314.124947-1-kamalheib1@gmail.com>

> From: Kamal Heib <kamalheib1@gmail.com>
> Sent: Monday, December 6, 2021 10:13 PM
>
> Fix the wrongly reported max_send_wr and max_recv_wr attributes for user
> QP by making sure to save their valuse on QP creation, so when query QP
> is called the attributes will be reported correctly.
> 
> Signed-off-by: Kamal Heib <kamalheib1@gmail.com>
> ---
>  drivers/infiniband/hw/qedr/verbs.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/infiniband/hw/qedr/verbs.c
> b/drivers/infiniband/hw/qedr/verbs.c
> index 9100009f0a23..a53476653b0d 100644
> --- a/drivers/infiniband/hw/qedr/verbs.c
> +++ b/drivers/infiniband/hw/qedr/verbs.c
> @@ -1931,6 +1931,7 @@ static int qedr_create_user_qp(struct qedr_dev
> *dev,
>  	/* db offset was calculated in copy_qp_uresp, now set in the user q
> */
>  	if (qedr_qp_has_sq(qp)) {
>  		qp->usq.db_addr = ctx->dpi_addr + uresp.sq_db_offset;
> +		qp->sq.max_wr = attrs->cap.max_send_wr;
>  		rc = qedr_db_recovery_add(dev, qp->usq.db_addr,
>  					  &qp->usq.db_rec_data->db_data,
>  					  DB_REC_WIDTH_32B,
> @@ -1941,6 +1942,7 @@ static int qedr_create_user_qp(struct qedr_dev
> *dev,
> 
>  	if (qedr_qp_has_rq(qp)) {
>  		qp->urq.db_addr = ctx->dpi_addr + uresp.rq_db_offset;
> +		qp->rq.max_wr = attrs->cap.max_recv_wr;
>  		rc = qedr_db_recovery_add(dev, qp->urq.db_addr,
>  					  &qp->urq.db_rec_data->db_data,
>  					  DB_REC_WIDTH_32B,
> --
> 2.31.1

Thanks, 

Acked-by: Michal Kalderon <michal.kalderon@marvell.com>



  parent reply	other threads:[~2021-12-07 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 20:13 [PATCH for-next] RDMA/qedr: Fix reporting max_{send/recv}_wr attrs Kamal Heib
2021-12-06 21:06 ` Jason Gunthorpe
2021-12-07  9:31   ` Kamal Heib
2021-12-07 10:56 ` Michal Kalderon [this message]
2021-12-07 19:04 ` Jason Gunthorpe

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=CH0PR18MB41292180806C1D1DF3E0DE58A16E9@CH0PR18MB4129.namprd18.prod.outlook.com \
    --to=mkalderon@marvell.com \
    --cc=aelior@marvell.com \
    --cc=jgg@ziepe.ca \
    --cc=kamalheib1@gmail.com \
    --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 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.