From: Jason Gunthorpe <jgg@nvidia.com>
To: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com, selvin.xavier@broadcom.com,
Kashyap Desai <kashyap.desai@broadcom.com>
Subject: Re: [PATCH rdma-rc] RDMA/bnxt_re: Fix budget handling of notification queue
Date: Mon, 7 Apr 2025 14:54:26 -0300 [thread overview]
Message-ID: <20250407175426.GA1729789@nvidia.com> (raw)
In-Reply-To: <20250324040935.90182-1-kalesh-anakkur.purayil@broadcom.com>
On Mon, Mar 24, 2025 at 09:39:35AM +0530, Kalesh AP wrote:
> From: Kashyap Desai <kashyap.desai@broadcom.com>
>
> The cited commit in Fixes tag introduced a bug which can cause hang
> of completion queue processing because of notification queue budget
> goes to zero.
>
> Found while doing nfs over rdma mount and umount.
> Below message is noticed because of the existing bug.
>
> kernel: cm_destroy_id_wait_timeout: cm_id=00000000ff6c6cc6 timed out. state 11 -> 0, refcnt=1
>
> Fix to handle this issue -
> Driver will not change nq->budget upon create and destroy of cq and srq
> rdma resources.
>
> Fixes: cb97b377a135 ("RDMA/bnxt_re: Refurbish CQ to NQ hash calculation")
> Signed-off-by: Kashyap Desai <kashyap.desai@broadcom.com>
> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> ---
> drivers/infiniband/hw/bnxt_re/ib_verbs.c | 5 -----
> 1 file changed, 5 deletions(-)
Applied to for-rc, thanks
Jason
prev parent reply other threads:[~2025-04-07 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 4:09 [PATCH rdma-rc] RDMA/bnxt_re: Fix budget handling of notification queue Kalesh AP
2025-04-07 17: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=20250407175426.GA1729789@nvidia.com \
--to=jgg@nvidia.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kashyap.desai@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.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.