From: sashiko-bot@kernel.org
To: "Praveen Kumar Kannoju" <praveen.kannoju@oracle.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2] RDMA/mlx5: Add poll-EQ callback for ULP recovery
Date: Mon, 21 Sep 2026 08:59:26 +0000 [thread overview]
Message-ID: <20260921085926.ABBB01F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260921085006.1443240-1-praveen.kannoju@oracle.com>
> Some upper layer protocols, such as RDS, use mlx5 RDMA CQs whose
> completion EQs are not shared with mlx5e queues. If an EQ notification is
> missed for one of those CQs, the ULP can remain idle until another event
> arrives or a driver health recovery path polls the EQ.
>
> mlx5e already has a recovery path that polls a completion EQ from the tx
> timeout handler through mlx5_eq_poll_irq_disabled(). That mechanism is
> internal to the mlx5 core and is not reachable from RDMA ULPs such as RDS
> when they need to recover a CQ-associated EQ.
>
> Add an optional RDMA device operation, reap_eq, and an ib_reap_eq() helper
> so ULPs can ask the provider to poll the event queue associated with a CQ.
> Providers that do not implement the callback return -EOPNOTSUPP.
>
> The recovery poll path is sleepable: mlx5 disables the IRQ synchronously
> [ ... ]
>
> Use this only as a recovery path for missed EQ notifications. It is not a
> normal completion polling path.
>
> Signed-off-by: Praveen Kumar Kannoju <praveen.kannoju@oracle.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260921085006.1443240-1-praveen.kannoju@oracle.com?part=1
next prev parent reply other threads:[~2026-09-21 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 8:50 [PATCH v2] RDMA/mlx5: Add poll-EQ callback for ULP recovery Praveen Kumar Kannoju
2026-09-21 8:59 ` sashiko-bot [this message]
2026-09-28 19:08 ` Leon Romanovsky
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=20260921085926.ABBB01F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=praveen.kannoju@oracle.com \
--cc=sashiko-reviews@lists.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