From: Yanjun Zhu <yanjun.zhu@oracle.com>
To: Jianchao Wang <jianchao.w.wang@oracle.com>,
monis@mellanox.com, dledford@redhat.com, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB/rxe: add RXE_START_MASK for rxe_opcode IB_OPCODE_RC_SEND_ONLY_INV
Date: Thu, 26 Apr 2018 12:02:40 +0800 [thread overview]
Message-ID: <f2df9d02-8693-60e6-e4fd-24c81817b898@oracle.com> (raw)
In-Reply-To: <1524714759-14654-1-git-send-email-jianchao.w.wang@oracle.com>
On 2018/4/26 11:52, Jianchao Wang wrote:
> w/o RXE_START_MASK, the last_psn of IB_OPCODE_RC_SEND_ONLY_INV
> will not be updated in update_wqe_psn, and the corresponding
> wqe will not be acked in rxe_completer due to its last_psn is
> zero. Finally, the other wqe will also not be able to be acked,
> because the wqe of IB_OPCODE_RC_SEND_ONLY_INV with last_psn 0
> is still there. This causes large amount of io timeout when
> nvmeof is over rxe.
>
> Add RXE_START_MASK for IB_OPCODE_RC_SEND_ONLY_INV to fix this.
>
> Signed-off-by: Jianchao Wang <jianchao.w.wang@oracle.com>
Reviewed-by: Zhu Yanjun <yanjun.zhu@oracle.com>
> ---
> drivers/infiniband/sw/rxe/rxe_opcode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_opcode.c b/drivers/infiniband/sw/rxe/rxe_opcode.c
> index 61927c1..4cf1106 100644
> --- a/drivers/infiniband/sw/rxe/rxe_opcode.c
> +++ b/drivers/infiniband/sw/rxe/rxe_opcode.c
> @@ -390,7 +390,7 @@ struct rxe_opcode_info rxe_opcode[RXE_NUM_OPCODE] = {
> .name = "IB_OPCODE_RC_SEND_ONLY_INV",
> .mask = RXE_IETH_MASK | RXE_PAYLOAD_MASK | RXE_REQ_MASK
> | RXE_COMP_MASK | RXE_RWR_MASK | RXE_SEND_MASK
> - | RXE_END_MASK,
> + | RXE_END_MASK | RXE_START_MASK,
> .length = RXE_BTH_BYTES + RXE_IETH_BYTES,
> .offset = {
> [RXE_BTH] = 0,
next prev parent reply other threads:[~2018-04-26 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 3:52 [PATCH] IB/rxe: add RXE_START_MASK for rxe_opcode IB_OPCODE_RC_SEND_ONLY_INV Jianchao Wang
2018-04-26 4:02 ` Yanjun Zhu [this message]
2018-04-27 18:23 ` Doug Ledford
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=f2df9d02-8693-60e6-e4fd-24c81817b898@oracle.com \
--to=yanjun.zhu@oracle.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jianchao.w.wang@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=monis@mellanox.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