From: Xiao Yang <yangx.jy@fujitsu.com>
To: <linux-rdma@vger.kernel.org>, <jgg@nvidia.com>, <rpearsonhpe@gmail.com>
Cc: <leon@kernel.org>, <lizhijian@fujitsu.com>, <y-goto@fujitsu.com>,
<zyjzyj2000@gmail.com>, Xiao Yang <yangx.jy@fujitsu.com>
Subject: [PATCH v7 0/8] RDMA/rxe: Add atomic write operation
Date: Thu, 1 Dec 2022 14:37:04 +0000 [thread overview]
Message-ID: <1669905432-14-1-git-send-email-yangx.jy@fujitsu.com> (raw)
The IB SPEC v1.5[1] defined new atomic write operation. This patchset
makes SoftRoCE support new atomic write on RC service.
On my rdma-core repository[2], I have introduced atomic write API
for libibverbs and Pyverbs. I also have provided a rdma_atomic_write
example and test_qp_ex_rc_atomic_write python test to verify
the patchset.
The steps to run the rdma_atomic_write example:
server:
$ ./rdma_atomic_write_server -s [server_address] -p [port_number]
client:
$ ./rdma_atomic_write_client -s [server_address] -p [port_number]
The steps to run test_qp_ex_rc_atomic_write test:
run_tests.py --dev rxe_enp0s3 --gid 1 -v test_qpex.QpExTestCase.test_qp_ex_rc_atomic_write
test_qp_ex_rc_atomic_write (tests.test_qpex.QpExTestCase) ... ok
----------------------------------------------------------------------
Ran 1 test in 0.013s
OK
[1]: https://www.infinibandta.org/wp-content/uploads/2021/08/IBTA-Overview-of-IBTA-Volume-1-Release-1.5-and-MPE-2021-08-17-Secure.pptx
[2]: https://github.com/yangx-jy/rdma-core/tree/new_api_with_point
v6->v7:
1) Rebase on current for-next
2) Define IB_WC_ATOMIC_WRITE in order
v5->v6:
1) Rebase on current for-next
2) Split the implementation of atomic write into 7 patches
3) Replace all "RDMA Atomic Write" with "atomic write"
4) Save 8-byte value in struct rxe_dma_info instead
5) Remove the print in atomic_write_reply()
v4->v5:
1) Rebase on current wip/jgg-for-next
2) Rewrite the implementation on responder
v3->v4:
1) Rebase on current wip/jgg-for-next
2) Fix a compiler error on 32-bit arch (e.g. parisc) by disabling RDMA Atomic Write
3) Replace 64-bit value with 8-byte array for atomic write
V2->V3:
1) Rebase
2) Add RDMA Atomic Write attribute for rxe device
V1->V2:
1) Set IB_OPCODE_RDMA_ATOMIC_WRITE to 0x1D
2) Add rdma.atomic_wr in struct rxe_send_wr and use it to pass the atomic write value
3) Use smp_store_release() to ensure that all prior operations have completed
Xiao Yang (8):
RDMA: Extend RDMA user ABI to support atomic write
RDMA: Extend RDMA kernel ABI to support atomic write
RDMA/rxe: Extend rxe user ABI to support atomic write
RDMA/rxe: Extend rxe packet format to support atomic write
RDMA/rxe: Make requester support atomic write on RC service
RDMA/rxe: Make responder support atomic write on RC service
RDMA/rxe: Implement atomic write completion
RDMA/rxe: Enable atomic write capability for rxe device
drivers/infiniband/sw/rxe/rxe_comp.c | 4 ++
drivers/infiniband/sw/rxe/rxe_opcode.c | 18 ++++++
drivers/infiniband/sw/rxe/rxe_opcode.h | 3 +
drivers/infiniband/sw/rxe/rxe_param.h | 5 ++
drivers/infiniband/sw/rxe/rxe_req.c | 15 ++++-
drivers/infiniband/sw/rxe/rxe_resp.c | 84 ++++++++++++++++++++++++--
include/rdma/ib_pack.h | 2 +
include/rdma/ib_verbs.h | 3 +
include/uapi/rdma/ib_user_verbs.h | 4 ++
include/uapi/rdma/rdma_user_rxe.h | 1 +
10 files changed, 132 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2022-12-01 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 14:37 Xiao Yang [this message]
2022-12-01 14:37 ` [PATCH v7 1/8] RDMA: Extend RDMA user ABI to support atomic write Xiao Yang
2022-12-01 14:37 ` [PATCH v7 2/8] RDMA: Extend RDMA kernel " Xiao Yang
2022-12-01 14:37 ` [PATCH v7 3/8] RDMA/rxe: Extend rxe user " Xiao Yang
2022-12-01 14:37 ` [PATCH v7 4/8] RDMA/rxe: Extend rxe packet format " Xiao Yang
2022-12-01 23:55 ` [PATCH v7 0/8] RDMA/rxe: Add atomic write operation Jason Gunthorpe
2022-12-02 5:37 ` Xiao Yang
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=1669905432-14-1-git-send-email-yangx.jy@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=rpearsonhpe@gmail.com \
--cc=y-goto@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 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).