From: Christian Berry via B4 Relay <devnull+christiankbberry.gmail.com@kernel.org>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Christian Berry <christiankbberry@gmail.com>
Subject: [PATCH] nvme: check for readiness more quickly to speed up boot
Date: Sun, 27 Sep 2026 19:03:49 -0400 [thread overview]
Message-ID: <20260927-nvme-ready-poll-v1-1-6a3f63b0ea3e@gmail.com> (raw)
From: Christian Berry <christiankbberry@gmail.com>
nvme_wait_ready() polls the controller status every 100ms, although
the controller may become ready much sooner. Every probe then waits
at least 100ms longer than needed, and possibly twice, since both
nvme_disable_ctrl() and nvme_enable_ctrl() wait for readiness.
Poll every millisecond instead, as Linux does since commit
3e98c2443f5c ("nvme: Check for readiness more quickly, to speed up
boot time"). The overall timeout is still based on elapsed time, so
it is unaffected.
Tested on an Arm64 SoC with a Samsung 980 SSD in a Gen3 x4
configuration, where PCIe + NVMe probe time dropped from 165 ms to
65 ms.
Signed-off-by: Christian Berry <christiankbberry@gmail.com>
---
drivers/nvme/host/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 345707ecfe..9686268d44 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -173,7 +173,7 @@ static int nvme_wait_ready(struct nvme_ctrl *ctrl, u64 cap, bool enabled)
if ((csts & NVME_CSTS_RDY) == bit)
break;
- mdelay(100);
+ udelay(1000);
if (is_timeout(start, timeout)) {
dev_err(ctrl->dev,
---
base-commit: 983608b439b803f72f12d56d0ab10bd6ba29e536
change-id: 20260927-nvme-ready-poll-4bd640377bab
Best regards,
--
Christian Berry <christiankbberry@gmail.com>
next reply other threads:[~2026-09-27 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 23:03 Christian Berry via B4 Relay [this message]
2026-09-28 8:19 ` Ahmad Fatoum
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=20260927-nvme-ready-poll-v1-1-6a3f63b0ea3e@gmail.com \
--to=devnull+christiankbberry.gmail.com@kernel.org \
--cc=barebox@lists.infradead.org \
--cc=christiankbberry@gmail.com \
--cc=s.hauer@pengutronix.de \
/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