From: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
To: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: "leon@kernel.org" <leon@kernel.org>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
Subject: Re: [RESEND PATCH v5 0/2] RDMA/rxe: Add RDMA Atomic Write operation
Date: Thu, 4 Aug 2022 07:30:20 +0000 [thread overview]
Message-ID: <d2ed21c9-ef86-8a83-425c-829f84a66a52@fujitsu.com> (raw)
In-Reply-To: <20220708040228.6703-1-yangx.jy@fujitsu.com>
Hi all,
Ping. Is it time to review the patch set?
Best Regards,
Xiao Yang
On 2022/7/8 12:02, Yang, Xiao/杨 晓 wrote:
> The IB SPEC v1.5[1] defined new RDMA Atomic Write operation. This
> patchset makes SoftRoCE support new RDMA Atomic Write on RC service.
>
> On my rdma-core repository[2], I have introduced RDMA Atomic Write API
> for libibverbs and Pyverbs. I also have provided a rdma_atomic_write
> example and test_qp_ex_rc_rdma_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_rdma_atomic_write test:
> run_tests.py --dev rxe_enp0s3 --gid 1 -v test_qpex.QpExTestCase.test_qp_ex_rc_rdma_atomic_write
> test_qp_ex_rc_rdma_atomic_write (tests.test_qpex.QpExTestCase) ... ok
>
> ----------------------------------------------------------------------
> Ran 1 test in 0.008s
>
> 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
>
> Note:
> This patch set depends on the following patch set:
> https://lore.kernel.org/linux-rdma/20220705145212.12014-1-yangx.jy@fujitsu.com/T/#t
>
> 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 RDMA 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 (2):
> RDMA/rxe: Support RDMA Atomic Write operation
> RDMA/rxe: Add RDMA Atomic Write attribute 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 | 94 ++++++++++++++++++++++++--
> 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, 142 insertions(+), 7 deletions(-)
>
prev parent reply other threads:[~2022-08-04 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 4:02 [RESEND PATCH v5 0/2] RDMA/rxe: Add RDMA Atomic Write operation yangx.jy
2022-07-08 4:02 ` [RESEND PATCH v5 1/2] RDMA/rxe: Support " yangx.jy
2022-09-23 22:22 ` Jason Gunthorpe
2022-09-26 6:55 ` Yang, Xiao/杨 晓
2022-10-06 7:53 ` Yang, Xiao/杨 晓
2022-10-14 16:00 ` Jason Gunthorpe
2022-10-20 13:25 ` Yang, Xiao/杨 晓
2022-10-24 17:02 ` Jason Gunthorpe
2022-09-27 8:18 ` Li Zhijian
2022-09-27 13:17 ` Jason Gunthorpe
2022-09-29 3:58 ` Yang, Xiao/杨 晓
2022-09-29 5:36 ` Yang, Xiao/杨 晓
2022-07-08 4:02 ` [RESEND PATCH v5 2/2] RDMA/rxe: Add RDMA Atomic Write attribute for rxe device yangx.jy
2022-08-04 7:30 ` yangx.jy [this message]
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=d2ed21c9-ef86-8a83-425c-829f84a66a52@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=rpearsonhpe@gmail.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