From: Li Zhijian <lizhijian@fujitsu.com>
To: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>,
linux-rdma@vger.kernel.org, leonro@nvidia.com, jgg@nvidia.com,
zyjzyj2000@gmail.com
Subject: Re: [PATCH 2/2] RDMA/rxe: Handle remote errors in the midst of a Read reply sequence
Date: Thu, 13 Oct 2022 13:36:17 +0800 [thread overview]
Message-ID: <bd695f2f-b2d2-02ef-bc4d-ba64e5cc59f9@fujitsu.com> (raw)
In-Reply-To: <20221013014724.3786212-2-matsuda-daisuke@fujitsu.com>
On 13/10/2022 09:47, Daisuke Matsuda wrote:
> Requesting nodes do not handle a reported error correctly if it is
> generated in the middle of multi-packet Read responses, and the node tries
> to resend the request endlessly. Let completer terminate the connection in
> that case.
>
> Signed-off-by: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>
> ---
> FOR REVIEWERS:
> I referred to IB Specification Vol 1-Revision-1.5 to make this patch.
> Please see Ch.9.9.2.2, Ch.9.9.2.4.2 and Table 59.
>
> drivers/infiniband/sw/rxe/rxe_comp.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_comp.c b/drivers/infiniband/sw/rxe/rxe_comp.c
> index fb0c008af78c..c9170dd99f3a 100644
> --- a/drivers/infiniband/sw/rxe/rxe_comp.c
> +++ b/drivers/infiniband/sw/rxe/rxe_comp.c
> @@ -200,6 +200,10 @@ static inline enum comp_state check_psn(struct rxe_qp *qp,
> */
> if (pkt->psn == wqe->last_psn)
> return COMPST_COMP_ACK;
> + else if (pkt->opcode == IB_OPCODE_RC_ACKNOWLEDGE &&
> + (qp->comp.opcode == IB_OPCODE_RC_RDMA_READ_RESPONSE_FIRST ||
> + qp->comp.opcode == IB_OPCODE_RC_RDMA_READ_RESPONSE_MIDDLE))
When IB_OPCODE_RC_RDMA_READ_RESPONSE_FIRST or IB_OPCODE_RC_RDMA_READ_RESPONSE_MIDDLE will be assigned to qp->comp.opcode ?
I wonder if "(pkt->opcode == IB_OPCODE_RC_ACKNOWLEDGE) " is enough ?
Thanks
Zhijian
> + return COMPST_CHECK_ACK;
> else
> return COMPST_DONE;
> } else if ((diff > 0) && (wqe->mask & WR_ATOMIC_OR_READ_MASK)) {
> @@ -228,6 +232,10 @@ static inline enum comp_state check_ack(struct rxe_qp *qp,
>
> case IB_OPCODE_RC_RDMA_READ_RESPONSE_FIRST:
> case IB_OPCODE_RC_RDMA_READ_RESPONSE_MIDDLE:
> + /* Check NAK code to handle a remote error */
> + if (pkt->opcode == IB_OPCODE_RC_ACKNOWLEDGE)
> + break;
> +
> if (pkt->opcode != IB_OPCODE_RC_RDMA_READ_RESPONSE_MIDDLE &&
> pkt->opcode != IB_OPCODE_RC_RDMA_READ_RESPONSE_LAST) {
> /* read retries of partial data may restart from
next prev parent reply other threads:[~2022-10-13 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 1:47 [PATCH 1/2] RDMA/rxe: Make responder handle RDMA Read failures Daisuke Matsuda
2022-10-13 1:47 ` [PATCH 2/2] RDMA/rxe: Handle remote errors in the midst of a Read reply sequence Daisuke Matsuda
2022-10-13 5:36 ` Li Zhijian [this message]
2022-10-14 2:35 ` matsuda-daisuke
2022-10-15 2:32 ` Li Zhijian
2022-10-13 4:14 ` [PATCH 1/2] RDMA/rxe: Make responder handle RDMA Read failures Li Zhijian
2022-10-24 17:10 ` 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=bd695f2f-b2d2-02ef-bc4d-ba64e5cc59f9@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matsuda-daisuke@fujitsu.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