From: Bob Pearson <rpearsonhpe@gmail.com>
To: jgg@nvidia.com, zyjzyj2000@gmail.com, lizhijian@fujitsu.com,
linux-rdma@vger.kernel.org
Cc: Bob Pearson <rpearsonhpe@gmail.com>
Subject: [PATCH 1/2] Update kernel headers
Date: Fri, 16 Sep 2022 22:15:36 -0500 [thread overview]
Message-ID: <20220917031536.21354-2-rpearsonhpe@gmail.com> (raw)
In-Reply-To: <20220917031536.21354-1-rpearsonhpe@gmail.com>
To commit ?? ("RDMA/rxe: Extend rxe_resp.c to support xrc qps").
Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
---
| 14 ++++++++++----
1 files changed, 10 insertions(+), 4 deletions(-)
--git a/kernel-headers/rdma/rdma_user_rxe.h b/kernel-headers/rdma/rdma_user_rxe.h
index 73f679df..c44db5fa 100644
--- a/kernel-headers/rdma/rdma_user_rxe.h
+++ b/kernel-headers/rdma/rdma_user_rxe.h
@@ -74,7 +74,7 @@ struct rxe_av {
struct rxe_send_wr {
__aligned_u64 wr_id;
- __u32 reserved;
+ __u32 srq_num; /* xrc only */
__u32 opcode;
__u32 send_flags;
union {
@@ -166,7 +173,7 @@ struct rxe_send_wqe {
struct rxe_recv_wqe {
__aligned_u64 wr_id;
- __u32 reserved;
+ __u32 num_sge;
__u32 padding;
struct rxe_dma_info dma;
};
@@ -191,8 +198,7 @@ struct rxe_create_qp_resp {
struct rxe_create_srq_resp {
struct mminfo mi;
- __u32 srq_num;
- __u32 reserved;
+ __u32 reserved[2];
};
struct rxe_modify_srq_cmd {
--
2.34.1
next prev parent reply other threads:[~2022-09-17 3:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 3:15 [PATCH 0/2] providers/rxe: Implement the xrc transport protocol Bob Pearson
2022-09-17 3:15 ` Bob Pearson [this message]
2022-09-17 3:15 ` [PATCH 2/2] " Bob Pearson
2022-09-26 17:58 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2022-09-13 22:30 [PATCH 0/2] providers/rxe: Remove redundant num_sge_fields Bob Pearson
2022-09-13 22:30 ` [PATCH 1/2] Update kernel headers Bob Pearson
2021-06-28 22:05 Bob Pearson
2021-06-29 6:36 ` Gal Pressman
2021-06-29 6:58 ` Leon Romanovsky
2021-06-29 14:09 ` Pearson, Robert B
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=20220917031536.21354-2-rpearsonhpe@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@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 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.