From: Jason Gunthorpe <jgg@ziepe.ca>
To: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
Cc: Yanjun Zhu <yanjun.zhu@linux.dev>,
Haakon Bugge <haakon.bugge@oracle.com>,
Cheng Xu <chengyou@linux.alibaba.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] RDMA/rxe: Fix no completion event issue
Date: Fri, 24 Jun 2022 20:39:53 -0300 [thread overview]
Message-ID: <20220624233953.GG23621@ziepe.ca> (raw)
In-Reply-To: <fa9863f0-d42e-f114-5321-108dda270e27@fujitsu.com>
On Tue, Jun 07, 2022 at 08:32:40AM +0000, lizhijian@fujitsu.com wrote:
> Hi Json & Yanjun
>
>
> I know there are still a few regressions on RXE, but i do wish you
> could take some time to review these *simple and bugfix* patches
> They are not related to the regressions.
I would like someone familiar with rxe to ack the datapath changes - I
have a very limited knowledge about rxe.
If that is not forthcoming from others in the rxe community then I
will accept confirmation directly from you that the pyverbs tests and
the blktests scenarios have been run and pass for your changes.
Jason
next prev parent reply other threads:[~2022-06-24 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 1:53 [PATCH v3 0/2] RDMA/rxe: Fix no completion event issue Li Zhijian
2022-05-16 1:53 ` [PATCH v3 1/2] RDMA/rxe: Update wqe_index for each wqe error completion Li Zhijian
2022-06-26 21:51 ` Bob Pearson
2022-06-27 3:41 ` lizhijian
2022-05-16 1:53 ` [PATCH v3 2/2] RDMA/rxe: Generate error completion for error requester QP state Li Zhijian
2022-06-26 22:42 ` Bob Pearson
2022-06-07 8:32 ` [PATCH v3 0/2] RDMA/rxe: Fix no completion event issue lizhijian
2022-06-24 23:39 ` Jason Gunthorpe [this message]
2022-06-25 7:47 ` Li, Zhijian
2022-06-25 12:59 ` Yanjun Zhu
2022-06-26 3:29 ` Li, Zhijian
2022-06-26 10:38 ` 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=20220624233953.GG23621@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=chengyou@linux.alibaba.com \
--cc=haakon.bugge@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=yanjun.zhu@linux.dev \
/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