archive mirror
 help / color / mirror / Atom feed
From: Bob Pearson <>
Cc: Bob Pearson <>
Subject: [PATCH 0/5] Providers/rxe: Implement XRC transport for rxe
Date: Fri, 30 Jul 2021 10:21:53 -0500	[thread overview]
Message-ID: <> (raw)

This set of patches implements xrc transport and extended srq required for
xrc transport in the rxe provider. It matches a kernel rxe driver patch
set with a similar name.

This patch set should be applied to the current rdma-core with the
"Replace AV by AH for UD sends (v2)" patch set which is a prerequisite.

With this patch set 4 of the 5 xrc tests in the python tests pass for
both regular and extended QP create verbs. The XRC/ODP test does not
pass since rxe does not currently support ODP.

Bob Pearson (5):
  Update kernel headers
  Providers/rxe: Support alloc/dealloc xrcd
  Providers/rxe: Support extended create srq
  Providers/rxe: Support get srq number
  Providers/rxe: Support XRC traffic

 kernel-headers/rdma/rdma_user_rxe.h |   6 +-
 providers/rxe/rxe-abi.h             |   2 +
 providers/rxe/rxe.c                 | 235 ++++++++++++++++++++++------
 providers/rxe/rxe.h                 |   5 +-
 4 files changed, 200 insertions(+), 48 deletions(-)


             reply	other threads:[~2021-07-30 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 15:21 Bob Pearson [this message]
2021-07-30 15:21 ` [PATCH 1/5] Update kernel headers Bob Pearson
2021-07-30 15:21 ` [PATCH 2/5] Providers/rxe: Support alloc/dealloc xrcd Bob Pearson
2021-07-30 15:21 ` [PATCH 3/5] Providers/rxe: Support extended create srq Bob Pearson
2021-07-30 15:21 ` [PATCH 4/5] Providers/rxe: Support get srq number Bob Pearson
2021-07-30 15:21 ` [PATCH 5/5] Providers/rxe: Support XRC traffic Bob Pearson
2021-08-02  8:30   ` Leon Romanovsky
2021-08-13 21:39     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).