From: Jason Gunthorpe <jgg@nvidia.com>
To: Xiao Yang <yangx.jy@fujitsu.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>,
"leon@kernel.org" <leon@kernel.org>,
"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
"y-goto@fujitsu.com" <y-goto@fujitsu.com>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>
Subject: Re: [PATCH v6 0/8] RDMA/rxe: Add atomic write operation
Date: Thu, 1 Dec 2022 08:58:30 -0400 [thread overview]
Message-ID: <Y4ik9iEfvMNefraR@nvidia.com> (raw)
In-Reply-To: <c10c62d4-fee9-4824-1383-8c6cdcf1c71c@fujitsu.com>
On Thu, Dec 01, 2022 at 07:58:44PM +0800, Xiao Yang wrote:
> On 2022/11/23 3:54, Jason Gunthorpe wrote:
> > On Sat, Oct 15, 2022 at 06:37:03AM +0000, yangx.jy@fujitsu.com wrote:
> > > 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.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
> > >
> > > 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()
> >
> > I think this looked OK, please fix the enum thing and also resolve all
> > the remarks on the github and rebase/repost/retest both series.
> Hi Jason,
>
> Thanks for your reminder. I will do it soon.
> In addition, I have resolved all remarks except the following one on github:
> EdwardSro: "keep an empty line at EoF"
> I: "I wonder why we need to add an empty line at EoF? I think there is no
> empty line at EOF in other files."
It is not really "empty line" it is that the last character in the
file should be '\n', and all files are like that.
Jason
next prev parent reply other threads:[~2022-12-01 12:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 6:37 [PATCH v6 0/8] RDMA/rxe: Add atomic write operation yangx.jy
2022-10-15 6:37 ` [PATCH v6 1/8] RDMA: Extend RDMA user ABI to support atomic write yangx.jy
2022-11-22 19:49 ` Jason Gunthorpe
2022-12-01 11:04 ` Xiao Yang
2022-10-15 6:37 ` [PATCH v6 2/8] RDMA: Extend RDMA kernel " yangx.jy
2022-10-15 6:37 ` [PATCH v6 3/8] RDMA/rxe: Extend rxe user " yangx.jy
2022-10-15 6:37 ` [PATCH v6 4/8] RDMA/rxe: Extend rxe packet format " yangx.jy
2022-10-15 6:37 ` [PATCH v6 6/8] RDMA/rxe: Make responder support atomic write on RC service yangx.jy
2022-10-15 6:37 ` [PATCH v6 5/8] RDMA/rxe: Make requester " yangx.jy
2022-10-15 6:37 ` [PATCH v6 7/8] RDMA/rxe: Implement atomic write completion yangx.jy
2022-10-15 6:37 ` [PATCH v6 8/8] RDMA/rxe: Enable atomic write capability for rxe device yangx.jy
2022-10-15 8:41 ` [PATCH v6 0/8] RDMA/rxe: Add atomic write operation Yang, Xiao/杨 晓
2022-11-22 19:54 ` Jason Gunthorpe
2022-12-01 11:58 ` Xiao Yang
2022-12-01 12:58 ` Jason Gunthorpe [this message]
2022-12-01 14:16 ` Xiao Yang
2022-12-01 14:45 ` Jason Gunthorpe
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=Y4ik9iEfvMNefraR@nvidia.com \
--to=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=yangx.jy@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.