From: sashiko-bot@kernel.org
To: "Nikhil P. Rao" <nikhil.rao@amd.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 2/3] RDMA/ionic: Use the ionic command timeout for the admin queue
Date: Tue, 03 Nov 2026 22:28:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-196112@kernel.org> (raw)
In-Reply-To: <20261102-b4-ionic-cmd-timeout-v1-2-2f75c2d0a0c7@amd.com>
> From: Arun Kumar Prakash <ArunKumar.Prakash@amd.com>
>
> Commit ec8ee714736e ("ionic: stretch heartbeat detection") notes that
> firmware can take more than 2 seconds to service a device or admin
> queue request, and is only expected to complete it within the ionic
> command timeout. The RDMA admin queue watchdog still uses 2 seconds,
> and when it fires it resets the RDMA LIF and every later verb fails
> with -ENODEV. Use the ionic command timeout, 5 seconds, instead. The
> AH create/destroy busy-wait keeps its fixed 2 second bound.
>
> Signed-off-by: Arun Kumar Prakash <ArunKumar.Prakash@amd.com>
> Reviewed-by: Brett Creeley <brett.creeley@amd.com>
> Acked-by: Allen Hubbe <allen.hubbe@amd.com>
> Signed-off-by: Nikhil P. Rao <nikhil.rao@amd.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261102-b4-ionic-cmd-timeout-v1-0-2f75c2d0a0c7@amd.com?part=2
next prev parent reply other threads:[~2026-11-03 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 22:27 [PATCH net-next 0/3] ionic: make the device command timeout configurable Nikhil P. Rao
2026-11-02 22:27 ` [PATCH net-next 1/3] ionic: make the command timeout per device Nikhil P. Rao
2026-11-03 22:28 ` sashiko-bot
2026-11-02 22:27 ` [PATCH net-next 2/3] RDMA/ionic: Use the ionic command timeout for the admin queue Nikhil P. Rao
2026-11-03 22:28 ` sashiko-bot [this message]
2026-11-02 22:27 ` [PATCH net-next 3/3] ionic: add devlink param for command timeout Nikhil P. Rao
2026-11-03 22:28 ` sashiko-bot
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=sashiko-outbox-196112@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nikhil.rao@amd.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