All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>,
	linux-rdma@vger.kernel.org, leon@kernel.org, jgg@ziepe.ca,
	zyjzyj2000@gmail.com
Cc: lizhijian@fujitsu.com
Subject: Re: [PATCH for-next v1 0/2] RDMA/rxe: RDMA FLUSH and ATOMIC WRITE with ODP
Date: Sat, 15 Mar 2025 20:21:16 +0100	[thread overview]
Message-ID: <1e4e16ab-4db4-471b-8c80-aae2e8886093@linux.dev> (raw)
In-Reply-To: <20250314081056.3496708-1-matsuda-daisuke@fujitsu.com>

在 2025/3/14 9:10, Daisuke Matsuda 写道:
> RDMA FLUSH[1] and ATOMIC WRITE[2] were added to rxe, but they cannot run
> in the ODP mode as of now. This series is for the kernel-side enablement.
> 
> There are also minor changes in libibverbs and pyverbs. The rdma-core tests
> are also added so that people can test the features.
> PR: https://github.com/linux-rdma/rdma-core/pull/1580
> 
> You can try the patches with the tree below:
> https://github.com/ddmatsu/linux/tree/odp-extension
> 
> Note that the tree is a bit old (6.13-rc1), because there was an issue[3]
> in the for-next tree that disabled ibv_query_device_ex(), which is used to
> query ODP capabilities. However, there is already a fix[4], and it is to be
> resolved in the next release. I will update the tree once it is ready.
> 
> [1] [for-next PATCH 00/10] RDMA/rxe: Add RDMA FLUSH operation
> https://lore.kernel.org/lkml/20221206130201.30986-1-lizhijian@fujitsu.com/
> 
> [2] [PATCH v7 0/8] RDMA/rxe: Add atomic write operation
> https://lore.kernel.org/linux-rdma/1669905432-14-1-git-send-email-yangx.jy@fujitsu.com/
> 
> [3] [bug report] RDMA/rxe: Failure of ibv_query_device() and ibv_query_device_ex() tests in rdma-core
> https://lore.kernel.org/all/1b9d6286-62fc-4b42-b304-0054c4ebee02@linux.dev/T/
> 
> [4] [PATCH rdma-rc 1/1] RDMA/rxe: Fix the failure of ibv_query_device() and ibv_query_device_ex() tests
> https://lore.kernel.org/linux-rdma/174102882930.42565.11864314726635251412.b4-ty@kernel.org/T/#t

Today I read these commits carefully. The 2 commits introduces 
ATOMIC_WRITE and ATOMIC_FLUSH operations with ODP enabled. In the 
rdma-core, the corresponding test cases are also added. I am fine with 
these 2 commits.

But I notice that there are no perftest results with the 2 operations. 
Perftest is a stress-test tools. With this tool, it can test the 2 
commits with some stress.

Anyway, I am fine with the 2 commits. It is better if the perftest 
results are attached.

Zhu Yanjun


> 
> Daisuke Matsuda (2):
>    RDMA/rxe: Enable ODP in RDMA FLUSH operation
>    RDMA/rxe: Enable ODP in ATOMIC WRITE operation
> 
>   drivers/infiniband/sw/rxe/rxe.c      |   2 +
>   drivers/infiniband/sw/rxe/rxe_loc.h  |  12 +++
>   drivers/infiniband/sw/rxe/rxe_mr.c   |   4 -
>   drivers/infiniband/sw/rxe/rxe_odp.c  | 132 ++++++++++++++++++++++++++-
>   drivers/infiniband/sw/rxe/rxe_resp.c |  18 ++--
>   include/rdma/ib_verbs.h              |   2 +
>   6 files changed, 155 insertions(+), 15 deletions(-)
> 


  parent reply	other threads:[~2025-03-15 19:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14  8:10 [PATCH for-next v1 0/2] RDMA/rxe: RDMA FLUSH and ATOMIC WRITE with ODP Daisuke Matsuda
2025-03-14  8:10 ` [PATCH for-next v1 1/2] RDMA/rxe: Enable ODP in RDMA FLUSH operation Daisuke Matsuda
2025-03-15 19:23   ` Zhu Yanjun
2025-03-17 18:22   ` Leon Romanovsky
2025-03-18  9:47     ` Daisuke Matsuda (Fujitsu)
2025-03-14  8:10 ` [PATCH for-next v1 2/2] RDMA/rxe: Enable ODP in ATOMIC WRITE operation Daisuke Matsuda
2025-03-15 19:23   ` Zhu Yanjun
2025-03-15 19:21 ` Zhu Yanjun [this message]
2025-03-17  5:22   ` [PATCH for-next v1 0/2] RDMA/rxe: RDMA FLUSH and ATOMIC WRITE with ODP Daisuke Matsuda (Fujitsu)

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=1e4e16ab-4db4-471b-8c80-aae2e8886093@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lizhijian@fujitsu.com \
    --cc=matsuda-daisuke@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.