From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Philipp Reisner <philipp.reisner@linbit.com>,
Daisuke Matsuda <matsuda-daisuke@fujitsu.com>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rdma_rxe: call comp_handler without holding cq->cq_lock
Date: Mon, 11 Aug 2025 06:48:59 -0700 [thread overview]
Message-ID: <2b593684-4409-485b-9edf-e44a402ecf3a@linux.dev> (raw)
In-Reply-To: <CADGDV=UgDb51nEtdide7k8==urCdrWcig8kBAY6k0PryR0c7xw@mail.gmail.com>
在 2025/8/10 22:26, Philipp Reisner 写道:
> On Thu, Aug 7, 2025 at 3:09 AM Zhu Yanjun <yanjun.zhu@linux.dev> wrote:
>>
>> 在 2025/8/6 5:39, Philipp Reisner 写道:
>>> Allow the comp_handler callback implementation to call ib_poll_cq().
>>> A call to ib_poll_cq() calls rxe_poll_cq() with the rdma_rxe driver.
>>> And rxe_poll_cq() locks cq->cq_lock. That leads to a spinlock deadlock.
>>>
>>> The Mellanox and Intel drivers allow a comp_handler callback
>>> implementation to call ib_poll_cq().
>>>
>>> Avoid the deadlock by calling the comp_handler callback without
>>> holding cq->cw_lock.
>>>
>>> Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
>>
>> ERROR: test_resize_cq (tests.test_cq.CQTest.test_resize_cq)
>> Test resize CQ, start with specific value and then increase and decrease
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>> File "/root/deb/rdma-core/tests/test_cq.py", line 135, in test_resize_cq
>> u.poll_cq(self.client.cq)
>> File "/root/deb/rdma-core/tests/utils.py", line 687, in poll_cq
>> wcs = _poll_cq(cq, count, data)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^
>> File "/root/deb/rdma-core/tests/utils.py", line 669, in _poll_cq
>> raise PyverbsError(f'Got timeout on polling ({count} CQEs remaining)')
>> pyverbs.pyverbs_error.PyverbsError: Got timeout on polling (1 CQEs
>> remaining)
>>
>> After I applied your patch in kervel v6.16, I got the above errors.
>>
>> Zhu Yanjun
>>
>
> Hello Zhu,
>
> When I run the test_resize_cq test in a loop (100 runs each) on the
> original code and with my patch, I get about the same failure rate.
Add Daisuke Matsuda
If I remember it correctly, when Daisuke and I discussed ODP patches, we
both made tests with rxe, from our tests results, it seems that this
test_resize_cq error does not occur.
Yanjun.Zhu
>
> without my patch success=87 failure=13
> without my patch success=82 failure=18
> without my patch success=81 failure=19
> with my patch success=89 failure=11
> with my patch success=90 failure=10
> with my patch success=82 failure=18
>
> The patch I am proposing does not change the failure rate of this test.
>
> Best regards,
> Philipp
>
> #!/bin/bash
>
> success=0
> failure=0
>
> for (( i = 0; i < 100; i++ )) do
> if rdma-core/build/bin/run_tests.py -k test_resize_cq; then
> success=$((success+1))
> else
> failure=$((failure+1))
> fi
> done
> echo success=$success failure=$failure
next prev parent reply other threads:[~2025-08-11 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 12:39 [PATCH] rdma_rxe: call comp_handler without holding cq->cq_lock Philipp Reisner
2025-08-07 1:09 ` Zhu Yanjun
2025-08-11 5:26 ` Philipp Reisner
2025-08-11 13:48 ` Zhu Yanjun [this message]
2025-08-12 15:54 ` Daisuke Matsuda
2025-08-14 5:33 ` Zhu Yanjun
2025-08-14 14:07 ` Daisuke Matsuda
[not found] ` <3cb43241-20d7-4ac9-b055-373fd058b3a3@linux.dev>
[not found] ` <2e645d1c-f853-4cee-9590-6f01820d027b@linux.dev>
2025-08-15 4:25 ` Zhu Yanjun
2025-08-15 18:29 ` Yanjun.Zhu
2025-08-16 15:57 ` Daisuke Matsuda
2025-08-19 2:37 ` Zhu Yanjun
2025-08-19 17:24 ` Philipp Reisner
2025-08-22 2:54 ` Zhu Yanjun
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=2b593684-4409-485b-9edf-e44a402ecf3a@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matsuda-daisuke@fujitsu.com \
--cc=philipp.reisner@linbit.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.