From: Jason Gunthorpe <jgg@nvidia.com>
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: Yanjun Zhu <yanjun.zhu@linux.dev>,
Haakon Bugge <haakon.bugge@oracle.com>,
linux-rdma@vger.kernel.org, Bob Pearson <rpearsonhpe@gmail.com>,
Leon Romanovsky <leon@kernel.org>,
Cheng Xu <chengyou@linux.alibaba.com>
Subject: Re: [PATCH RESEND for-next v6 0/4] RDMA/rxe: Fix no completion event issue
Date: Tue, 2 Aug 2022 13:54:47 -0300 [thread overview]
Message-ID: <YulW1zDe+mc6ZUi/@nvidia.com> (raw)
In-Reply-To: <1658307368-1851-1-git-send-email-lizhijian@fujitsu.com>
On Wed, Jul 20, 2022 at 04:56:04AM -0400, Li Zhijian wrote:
> No change since v5, just resend it via another smtp instead of
> Microsoft Exchange which made patches messed up.
>
> It's observed that no more completion occurs after a few incorrect posts.
> Actually, it will block the polling. we can easily reproduce it by the below
> pattern.
>
> a. post correct RDMA_WRITE
> b. poll completion event
> while true {
> c. post incorrect RDMA_WRITE(wrong rkey for example)
> d. poll completion event <<<< block after 2 incorrect RDMA_WRITE posts
> }
>
> V4 add new patch from Bob where it make requester stop executing qp
> operation as soon as possible.
>
> Both blktests and pyverbs tests are passed fine.
>
> Bob Pearson (1):
> RDMA/rxe: Split qp state for requester and completer
>
> Li Zhijian (3):
> RDMA/rxe: Update wqe_index for each wqe error completion
> RDMA/rxe: Generate error completion for error requester QP state
> RDMA/rxe: Fix typo in comment
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2022-08-02 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 8:56 [PATCH RESEND for-next v6 0/4] RDMA/rxe: Fix no completion event issue Li Zhijian
2022-07-20 8:56 ` [PATCH RESEND for-next v6 1/4] RDMA/rxe: Update wqe_index for each wqe error completion Li Zhijian
2022-07-20 8:56 ` [PATCH RESEND for-next v6 2/4] RDMA/rxe: Generate error completion for error requester QP state Li Zhijian
2022-07-20 8:56 ` [PATCH RESEND for-next v6 3/4] RDMA/rxe: Split qp state for requester and completer Li Zhijian
2022-07-20 8:56 ` [PATCH RESEND for-next v6 4/4] RDMA/rxe: Fix typo in comment Li Zhijian
2022-07-29 19:48 ` [PATCH RESEND for-next v6 0/4] RDMA/rxe: Fix no completion event issue Jason Gunthorpe
2022-08-01 19:24 ` Bob Pearson
2022-08-02 16:54 ` Jason Gunthorpe [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=YulW1zDe+mc6ZUi/@nvidia.com \
--to=jgg@nvidia.com \
--cc=chengyou@linux.alibaba.com \
--cc=haakon.bugge@oracle.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=rpearsonhpe@gmail.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