From: Li Zhijian <lizhijian@fujitsu.com>
To: <linux-rdma@vger.kernel.org>, <zyjzyj2000@gmail.com>,
<jgg@ziepe.ca>, <aharonl@nvidia.com>, <leon@kernel.org>,
<tom@talpey.com>, <tomasz.gromadzki@intel.com>
Cc: <linux-kernel@vger.kernel.org>, <mbloch@nvidia.com>,
<liangwenpeng@huawei.com>, <yangx.jy@fujitsu.com>,
<y-goto@fujitsu.com>, <rpearsonhpe@gmail.com>,
<dan.j.williams@intel.com>, Li Zhijian <lizhijian@fujitsu.com>
Subject: [RFC PATCH v3 5/7] RDMA/rxe: Implement flush completion
Date: Tue, 15 Mar 2022 18:18:43 +0800 [thread overview]
Message-ID: <20220315101845.4166983-6-lizhijian@fujitsu.com> (raw)
In-Reply-To: <20220315101845.4166983-1-lizhijian@fujitsu.com>
Introduce a new IB_UVERBS_WC_FLUSH code to tell userspace a FLUSH
completion.
Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
---
drivers/infiniband/sw/rxe/rxe_comp.c | 4 +++-
include/rdma/ib_verbs.h | 1 +
include/uapi/rdma/ib_user_verbs.h | 1 +
3 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/infiniband/sw/rxe/rxe_comp.c b/drivers/infiniband/sw/rxe/rxe_comp.c
index f363fe3fa414..e5b9d07eba93 100644
--- a/drivers/infiniband/sw/rxe/rxe_comp.c
+++ b/drivers/infiniband/sw/rxe/rxe_comp.c
@@ -104,6 +104,7 @@ static enum ib_wc_opcode wr_to_wc_opcode(enum ib_wr_opcode opcode)
case IB_WR_LOCAL_INV: return IB_WC_LOCAL_INV;
case IB_WR_REG_MR: return IB_WC_REG_MR;
case IB_WR_BIND_MW: return IB_WC_BIND_MW;
+ case IB_WR_RDMA_FLUSH: return IB_WC_RDMA_FLUSH;
default:
return 0xff;
@@ -261,7 +262,8 @@ static inline enum comp_state check_ack(struct rxe_qp *qp,
*/
case IB_OPCODE_RC_RDMA_READ_RESPONSE_MIDDLE:
if (wqe->wr.opcode != IB_WR_RDMA_READ &&
- wqe->wr.opcode != IB_WR_RDMA_READ_WITH_INV) {
+ wqe->wr.opcode != IB_WR_RDMA_READ_WITH_INV &&
+ wqe->wr.opcode != IB_WR_RDMA_FLUSH) {
wqe->status = IB_WC_FATAL_ERR;
return COMPST_ERROR;
}
diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h
index 8f04e45b56aa..a73c746759b0 100644
--- a/include/rdma/ib_verbs.h
+++ b/include/rdma/ib_verbs.h
@@ -965,6 +965,7 @@ const char *__attribute_const__ ib_wc_status_msg(enum ib_wc_status status);
enum ib_wc_opcode {
IB_WC_SEND = IB_UVERBS_WC_SEND,
IB_WC_RDMA_WRITE = IB_UVERBS_WC_RDMA_WRITE,
+ IB_WC_RDMA_FLUSH = IB_UVERBS_WC_FLUSH,
IB_WC_RDMA_READ = IB_UVERBS_WC_RDMA_READ,
IB_WC_COMP_SWAP = IB_UVERBS_WC_COMP_SWAP,
IB_WC_FETCH_ADD = IB_UVERBS_WC_FETCH_ADD,
diff --git a/include/uapi/rdma/ib_user_verbs.h b/include/uapi/rdma/ib_user_verbs.h
index 69a04bb828a0..a8ba12aa04e6 100644
--- a/include/uapi/rdma/ib_user_verbs.h
+++ b/include/uapi/rdma/ib_user_verbs.h
@@ -476,6 +476,7 @@ enum ib_uverbs_wc_opcode {
IB_UVERBS_WC_BIND_MW = 5,
IB_UVERBS_WC_LOCAL_INV = 6,
IB_UVERBS_WC_TSO = 7,
+ IB_UVERBS_WC_FLUSH = 8,
};
struct ib_uverbs_wc {
--
2.31.1
next prev parent reply other threads:[~2022-03-15 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 10:18 [RFC PATCH v3 0/7] RDMA/rxe: Add RDMA FLUSH operation Li Zhijian
2022-03-15 10:18 ` [RFC PATCH v3 1/7] RDMA: Allow registering MR with flush access flags Li Zhijian
2022-03-15 10:18 ` [RFC PATCH v3 2/7] RDMA/rxe: Allow registering persistent flag for pmem MR only Li Zhijian
2022-03-15 10:18 ` [RFC PATCH v3 3/7] RDMA/rxe: Implement RC RDMA FLUSH service in requester side Li Zhijian
2022-03-15 10:18 ` [RFC PATCH v3 4/7] RDMA/rxe: Implement flush execution in responder side Li Zhijian
2022-03-15 10:18 ` Li Zhijian [this message]
2022-03-15 10:18 ` [RFC PATCH v3 6/7] RDMA/rxe: Enable RDMA FLUSH capability for rxe device Li Zhijian
2022-03-15 10:18 ` [RFC PATCH v3 7/7] RDMA/rxe: Add RD FLUSH service support Li Zhijian
2022-03-25 7:34 ` [RFC PATCH v3 0/7] RDMA/rxe: Add RDMA FLUSH operation lizhijian
2022-07-04 13:26 ` 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=20220315101845.4166983-6-lizhijian@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=aharonl@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=liangwenpeng@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=rpearsonhpe@gmail.com \
--cc=tom@talpey.com \
--cc=tomasz.gromadzki@intel.com \
--cc=y-goto@fujitsu.com \
--cc=yangx.jy@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;
as well as URLs for NNTP newsgroup(s).