From: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
To: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
Yanjun Zhu <yanjun.zhu@linux.dev>, Jason Gunthorpe <jgg@ziepe.ca>,
Haakon Bugge <haakon.bugge@oracle.com>,
Cheng Xu <chengyou@linux.alibaba.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] RDMA/rxe: Fix no completion event issue
Date: Sun, 26 Jun 2022 10:38:42 +0000 [thread overview]
Message-ID: <14b8089b-586e-7240-1f3a-e36cbab7f7ba@fujitsu.com> (raw)
In-Reply-To: <83cfdf23-7a2d-0776-85ee-7314187e9980@fujitsu.com>
On 2022/6/26 11:29, Li, Zhijian wrote:
> + Xiao
> I do believe regression is high priority, and I'm very willing to
> contribute our efforts to improve the stability of RXE :)
> Yang,Xiao and me tried to reproduce the issues in maillist and we also
> tried to review the their corresponding patches.
> However actually we didn't find a unified way something like bugzilla to
> maintain the issues and their status, and most of
> them are not reproduced by our local environment. So it's a bit hard for
> us to review/verify the patches especially for the
> large/complicate patch if we don't have the use cases.
>
> BTW, IMO we shouldn't stop reviewing other fixes expect recent regressions.
Agreed.
Besides, this patch set looks good to me.
Reviewed-by: Xiao Yang <yangx.jy@fujitsu.com>
Best Regards,
Xiao Yang
>
> Zhijian
prev parent reply other threads:[~2022-06-26 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 1:53 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
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 [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=14b8089b-586e-7240-1f3a-e36cbab7f7ba@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=chengyou@linux.alibaba.com \
--cc=haakon.bugge@oracle.com \
--cc=jgg@ziepe.ca \
--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
all inboxes | Powered by JetHome®