From: Bob Pearson <rpearsonhpe@gmail.com>
To: jgg@nvidia.com, zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Cc: Bob Pearson <rpearson@hpe.com>
Subject: [PATCH for-next v3 0/9] RDMA/rxe: Implement memory windows
Date: Wed, 21 Apr 2021 00:20:07 -0500 [thread overview]
Message-ID: <20210421052015.4546-1-rpearson@hpe.com> (raw)
This series of patches implement memory windows for the rdma_rxe
driver. This is a shorter reimplementation of an earlier patch
set. They apply to and depend on the current for-next linux rdma
tree.
Signed-off-by: Bob Pearson <rpearson@hpe.com>
---
v3:
cleaned up void return and lower case enums from
Zhu's review.
v2:
cleaned up an issue in rdma_user_rxe.h
cleaned up a collision in rxe_resp.c
Bob Pearson (9):
RDMA/rxe: Add bind MW fields to rxe_send_wr
RDMA/rxe: Return errors for add index and key
RDMA/rxe: Enable MW object pool
RDMA/rxe: Add ib_alloc_mw and ib_dealloc_mw verbs
RDMA/rxe: Replace WR_REG_MASK by WR_LOCAL_OP_MASK
RDMA/rxe: Move local ops to subroutine
RDMA/rxe: Add support for bind MW work requests
RDMA/rxe: Implement invalidate MW operations
RDMA/rxe: Implement memory access through MWs
drivers/infiniband/sw/rxe/Makefile | 1 +
drivers/infiniband/sw/rxe/rxe.c | 1 +
drivers/infiniband/sw/rxe/rxe_comp.c | 1 +
drivers/infiniband/sw/rxe/rxe_loc.h | 29 +-
drivers/infiniband/sw/rxe/rxe_mr.c | 79 ++++--
drivers/infiniband/sw/rxe/rxe_mw.c | 356 +++++++++++++++++++++++++
drivers/infiniband/sw/rxe/rxe_opcode.c | 11 +-
drivers/infiniband/sw/rxe/rxe_opcode.h | 3 +-
drivers/infiniband/sw/rxe/rxe_param.h | 19 +-
drivers/infiniband/sw/rxe/rxe_pool.c | 45 ++--
drivers/infiniband/sw/rxe/rxe_pool.h | 8 +-
drivers/infiniband/sw/rxe/rxe_req.c | 102 ++++---
drivers/infiniband/sw/rxe/rxe_resp.c | 110 +++++---
drivers/infiniband/sw/rxe/rxe_verbs.c | 5 +-
drivers/infiniband/sw/rxe/rxe_verbs.h | 38 ++-
include/uapi/rdma/rdma_user_rxe.h | 34 ++-
16 files changed, 691 insertions(+), 151 deletions(-)
create mode 100644 drivers/infiniband/sw/rxe/rxe_mw.c
--
2.27.0
next reply other threads:[~2021-04-21 5:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 5:20 Bob Pearson [this message]
2021-04-21 5:20 ` [PATCH for-next v3 1/9] RDMA/rxe: Add bind MW fields to rxe_send_wr Bob Pearson
2021-04-21 5:20 ` [PATCH for-next v3 2/9] RDMA/rxe: Return errors for add index and key Bob Pearson
2021-04-21 5:20 ` [PATCH for-next v3 3/9] RDMA/rxe: Enable MW object pool Bob Pearson
2021-04-21 5:20 ` [PATCH for-next v3 4/9] RDMA/rxe: Add ib_alloc_mw and ib_dealloc_mw verbs Bob Pearson
2021-04-21 5:54 ` Zhu Yanjun
2021-04-21 6:20 ` Leon Romanovsky
2021-04-21 6:26 ` Zhu Yanjun
2021-04-21 5:20 ` [PATCH for-next v3 5/9] RDMA/rxe: Replace WR_REG_MASK by WR_LOCAL_OP_MASK Bob Pearson
2021-04-21 5:20 ` [PATCH for-next v3 6/9] RDMA/rxe: Move local ops to subroutine Bob Pearson
2021-04-21 5:20 ` [PATCH for-next v3 7/9] RDMA/rxe: Add support for bind MW work requests Bob Pearson
2021-04-21 9:36 ` Zhu Yanjun
2021-04-21 15:21 ` Robert Pearson
2021-04-22 5:33 ` Bob Pearson
2021-04-21 5:20 ` [PATCH for-next v3 8/9] RDMA/rxe: Implement invalidate MW operations Bob Pearson
2021-04-21 5:20 ` [PATCH for-next v3 9/9] RDMA/rxe: Implement memory access through MWs 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=20210421052015.4546-1-rpearson@hpe.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearson@hpe.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).