From: Jason Gunthorpe <jgg@ziepe.ca>
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, Xiao Yang <yangx.jy@fujitsu.com>,
y-goto@fujitsu.com, Bob Pearson <rpearsonhpe@gmail.com>,
Mark Bloch <mbloch@nvidia.com>,
Aharon Landau <aharonl@nvidia.com>, Tom Talpey <tom@talpey.com>,
tomasz.gromadzki@intel.com,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org,
Wenpeng Liang <liangwenpeng@huawei.com>
Subject: Re: [PATCH v4 0/6] RDMA/rxe: Add RDMA FLUSH operation
Date: Fri, 26 Aug 2022 10:37:55 -0300 [thread overview]
Message-ID: <YwjMs4wKm7CHzTuf@ziepe.ca> (raw)
In-Reply-To: <1659685579-2-1-git-send-email-lizhijian@fujitsu.com>
On Fri, Aug 05, 2022 at 07:46:13AM +0000, Li Zhijian wrote:
> Hey folks,
>
> It's been a long time since the 3rd, in the meantime, some RXE regressions have
> been fixed by comminity. So It'd like to post my 4th version. feedbacks are
> very welcome :).
I think enough work is done to start going forward with new features
Are there any comments on this series?
Jason
next prev parent reply other threads:[~2022-08-26 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 7:46 [PATCH v4 0/6] RDMA/rxe: Add RDMA FLUSH operation Li Zhijian
2022-08-05 7:46 ` [PATCH v4 1/6] RDMA: Allow registering MR with flush access flags Li Zhijian
2022-08-05 7:46 ` [PATCH v4 2/6] RDMA/rxe: Allow registering persistent flag for pmem MR only Li Zhijian
2022-08-05 7:46 ` [PATCH v4 3/6] RDMA/rxe: Implement RC RDMA FLUSH service in requester side Li Zhijian
2022-08-05 7:46 ` [PATCH v4 4/6] RDMA/rxe: Implement flush execution in responder side Li Zhijian
2022-08-05 7:55 ` [PATCH v4 5/6] RDMA/rxe: Implement flush completion Li Zhijian
2022-08-05 7:55 ` [PATCH v4 6/6] RDMA/rxe: Enable RDMA FLUSH capability for rxe device Li Zhijian
2022-08-26 13:37 ` Jason Gunthorpe [this message]
2022-08-29 1:36 ` [PATCH v4 0/6] RDMA/rxe: Add RDMA FLUSH operation yangx.jy
2022-08-29 1:40 ` yangx.jy
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=YwjMs4wKm7CHzTuf@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=aharonl@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=leon@kernel.org \
--cc=liangwenpeng@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=mbloch@nvidia.com \
--cc=rpearsonhpe@gmail.com \
--cc=tom@talpey.com \
--cc=tomasz.gromadzki@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox