From: Bob Pearson <rpearsonhpe@gmail.com>
To: jgg@nvidia.com, zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Cc: Bob Pearson <rpearsonhpe@gmail.com>
Subject: [PATCH for-next v2 0/2] Let RDMA-core manage certain objects
Date: Thu, 29 Jul 2021 17:30:09 -0500 [thread overview]
Message-ID: <20210729223010.31007-1-rpearsonhpe@gmail.com> (raw)
The rxe driver duplicates work already done by rdma core. These patches
simplify the rxe driver removing the duplicate effort. The first patch
was already released. Version 2 adds a second patch.
These two patches should be applied after V2 "Three rxe bug fixes"
patches and V3 "Replace AV by AH in UD sends" patches applied to
the current for-next branch.
Bob Pearson (2):
RDMA/rxe: Let rdma-core manage PDs
RDMA/rxe: Let rdma-core manage CQs and SRQs
drivers/infiniband/sw/rxe/rxe_av.c | 2 +-
drivers/infiniband/sw/rxe/rxe_comp.c | 14 ++--
drivers/infiniband/sw/rxe/rxe_loc.h | 19 +-----
drivers/infiniband/sw/rxe/rxe_mr.c | 8 +--
drivers/infiniband/sw/rxe/rxe_mw.c | 31 ++++-----
drivers/infiniband/sw/rxe/rxe_net.c | 6 +-
drivers/infiniband/sw/rxe/rxe_qp.c | 92 +++++++++------------------
drivers/infiniband/sw/rxe/rxe_recv.c | 6 +-
drivers/infiniband/sw/rxe/rxe_req.c | 22 +++----
drivers/infiniband/sw/rxe/rxe_resp.c | 58 ++++++++---------
drivers/infiniband/sw/rxe/rxe_verbs.c | 44 +++++--------
drivers/infiniband/sw/rxe/rxe_verbs.h | 59 ++++++++++++++---
12 files changed, 165 insertions(+), 196 deletions(-)
--
2.30.2
next reply other threads:[~2021-07-29 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 22:30 Bob Pearson [this message]
2021-07-29 22:30 ` [PATCH for-next v2 1/2] RDMA/rxe: Let rdma-core manage PDs Bob Pearson
2021-07-29 22:30 ` [PATCH for-next v2 2/2] RDMA/rxe: Let rdma-core manage CQs and SRQs Bob Pearson
2021-08-27 12:58 ` [PATCH for-next v2 0/2] Let RDMA-core manage certain objects 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=20210729223010.31007-1-rpearsonhpe@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.