From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: Bob Pearson <rpearsonhpe@gmail.com>,
jgg@nvidia.com, zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH] Subject: [PATCH for-next] RDMA/rxe: Fix "Soft RoCE Driver"
Date: Sat, 16 Apr 2022 18:03:22 +0800 [thread overview]
Message-ID: <77223356-6762-aa69-1cb3-480b41b45d97@linux.dev> (raw)
In-Reply-To: <20220416063312.7777-1-rpearsonhpe@gmail.com>
在 2022/4/16 14:33, Bob Pearson 写道:
> The rping benchmark fails on long runs. The root cause of this
> failure has been traced to a failure to compute a nonzero value of mr
> in rare situations.
>
> Fix this failure by correctly handling the computation of mr in
> read_reply() in rxe_resp.c in the replay flow.
>
> Fixes: 8700e3e7c485 ("Soft RoCE driver")
Fixes should be 8a1a0be894da ("RDMA/rxe: Replace mr by rkey in responder
resources")
> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> ---
> drivers/infiniband/sw/rxe/rxe_resp.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_resp.c b/drivers/infiniband/sw/rxe/rxe_resp.c
> index e2653a8721fe..2e627685e804 100644
> --- a/drivers/infiniband/sw/rxe/rxe_resp.c
> +++ b/drivers/infiniband/sw/rxe/rxe_resp.c
> @@ -734,8 +734,14 @@ static enum resp_states read_reply(struct rxe_qp *qp,
> }
>
> if (res->state == rdatm_res_state_new) {
> - mr = qp->resp.mr;
> - qp->resp.mr = NULL;
> + if (!res->replay) {
> + mr = qp->resp.mr;
> + qp->resp.mr = NULL;
> + } else {
> + mr = rxe_recheck_mr(qp, res->read.rkey);
> + if (!mr)
> + return RESPST_ERR_RKEY_VIOLATION;
> + }
>
> if (res->read.resid <= mtu)
> opcode = IB_OPCODE_RC_RDMA_READ_RESPONSE_ONLY;
>
> base-commit: 98c8026331ceabe1df579940b81eec75eb49cdd9
next prev parent reply other threads:[~2022-04-16 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 6:33 [PATCH] Subject: [PATCH for-next] RDMA/rxe: Fix "Soft RoCE Driver" Bob Pearson
2022-04-16 10:03 ` Yanjun Zhu [this message]
2022-04-16 15:20 ` Bob Pearson
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=77223356-6762-aa69-1cb3-480b41b45d97@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=zyjzyj2000@gmail.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