From: Leon Romanovsky <leon@kernel.org>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: jgg@nvidia.com, xyjxyj2000@gmail.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH 5/5] Providers/rxe: Support XRC traffic
Date: Mon, 2 Aug 2021 11:30:27 +0300 [thread overview]
Message-ID: <YQetIxKBrtpBvL5Y@unreal> (raw)
In-Reply-To: <20210730152157.67592-6-rpearsonhpe@gmail.com>
On Fri, Jul 30, 2021 at 10:21:58AM -0500, Bob Pearson wrote:
> Extended create_qp and create_qp_ex verbs to support XRC QP types.
> Extended WRs to support XRC operations.
>
> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> ---
> providers/rxe/rxe.c | 132 ++++++++++++++++++++++++++++++++------------
> 1 file changed, 96 insertions(+), 36 deletions(-)
<...>
> +static void wr_set_xrc_srqn(struct ibv_qp_ex *ibqp, uint32_t remote_srqn)
> +{
> + struct rxe_qp *qp = container_of(ibqp, struct rxe_qp, vqp.qp_ex);
> + struct rxe_send_wqe *wqe = addr_from_index(qp->sq.queue,
> + qp->cur_index - 1);
> +
> + if (qp->err)
> + return;
Why is that?
> +
> + wqe->wr.wr.xrc.srq_num = remote_srqn;
> +}
> +
next prev parent reply other threads:[~2021-08-02 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 15:21 [PATCH 0/5] Providers/rxe: Implement XRC transport for rxe Bob Pearson
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 [this message]
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:
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=YQetIxKBrtpBvL5Y@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=xyjxyj2000@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).