From: Leon Romanovsky <leon@kernel.org>
To: Prabhath Sajeepa <psajeepa@purestorage.com>
Cc: dledford@redhat.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, roland@purestorage.com
Subject: Re: [PATCH] IB/mlx5: Fix outstanding_pi index for GSI qps
Date: Sun, 15 Dec 2019 20:55:00 +0200 [thread overview]
Message-ID: <20191215185500.GA6097@unreal> (raw)
In-Reply-To: <1576195889-23527-1-git-send-email-psajeepa@purestorage.com>
On Thu, Dec 12, 2019 at 05:11:29PM -0700, Prabhath Sajeepa wrote:
> b0ffeb537f3a changed the way how outstanding WRs are tracked for GSI QP. But the
> fix did not cover the case when a call to ib_post_send fails and index
> to track outstanding WRs need to be updated correctly.
>
> Fixes: b0ffeb537f3a ('IB/mlx5: Fix iteration overrun in GSI qps ')
> Signed-off-by: Prabhath Sajeepa <psajeepa@purestorage.com>
> ---
> drivers/infiniband/hw/mlx5/gsi.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/infiniband/hw/mlx5/gsi.c b/drivers/infiniband/hw/mlx5/gsi.c
> index ac4d8d1..1ae6fd9 100644
> --- a/drivers/infiniband/hw/mlx5/gsi.c
> +++ b/drivers/infiniband/hw/mlx5/gsi.c
> @@ -507,8 +507,7 @@ int mlx5_ib_gsi_post_send(struct ib_qp *qp, const struct ib_send_wr *wr,
> ret = ib_post_send(tx_qp, &cur_wr.wr, bad_wr);
> if (ret) {
> /* Undo the effect of adding the outstanding wr */
> - gsi->outstanding_pi = (gsi->outstanding_pi - 1) %
> - gsi->cap.max_send_wr;
> + gsi->outstanding_pi--;
I'm a little bit confused, what is the difference before and after
except dropping "gsi->cap.max_send_wr"?
Thanks
> goto err;
> }
> spin_unlock_irqrestore(&gsi->lock, flags);
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-12-15 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 0:11 [PATCH] IB/mlx5: Fix outstanding_pi index for GSI qps Prabhath Sajeepa
2019-12-15 18:55 ` Leon Romanovsky [this message]
[not found] ` <CAE=VkfD0Ywey6wW_rOZ=4qGyW347kTXH_MM17NvQhy6bkT=+tw@mail.gmail.com>
2019-12-16 17:51 ` Leon Romanovsky
2019-12-16 19:01 ` Prabhath Sajeepa
2019-12-18 6:00 ` Leon Romanovsky
2020-01-03 20:01 ` 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=20191215185500.GA6097@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=psajeepa@purestorage.com \
--cc=roland@purestorage.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