From: Minwoo Im <minwoo.im.dev@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Minwoo Im <minwoo.im.dev@gmail.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: [PATCH 2/3] nvme: check all retry delay times in Identify Controller
Date: Fri, 8 Jan 2021 23:46:58 +0900 [thread overview]
Message-ID: <20210108144659.7126-3-minwoo.im.dev@gmail.com> (raw)
In-Reply-To: <20210108144659.7126-1-minwoo.im.dev@gmail.com>
If none of Command Retry Delay Time(CRDT)s are set, then we can simply
skip to configure Advanced Command Retry Enable(ACRE).
CRDT selection will be made in Completion Queue Entry that controller
has responsibility to decide.
This patch checks all CRDT[0, 1, and 2] in Identify Controller data
structrure instead of checking the first one: CRDT[0].
Signed-off-by: Minwoo Im <minwoo.im.dev@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 d0c99a9400ea..6e428fdc25a8 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -2501,7 +2501,7 @@ static int nvme_configure_acre(struct nvme_ctrl *ctrl)
int ret;
/* Don't bother enabling the feature if retry delay is not reported */
- if (!ctrl->crdt[0])
+ if (!ctrl->crdt[0] && !ctrl->crdt[1] && !ctrl->crdt[2])
return 0;
host = kzalloc(sizeof(*host), GFP_KERNEL);
--
2.17.1
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-01-08 14:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 14:46 [PATCH 0/3] nvme: fixes for command retry Minwoo Im
2021-01-08 14:46 ` [PATCH 1/3] nvme: support command retry delay for admin command Minwoo Im
2021-01-09 20:34 ` Chaitanya Kulkarni
2021-01-10 1:33 ` Minwoo Im
2021-01-12 8:06 ` Christoph Hellwig
2021-01-12 8:06 ` Christoph Hellwig
2021-01-12 8:47 ` Minwoo Im
2021-01-14 7:22 ` Christoph Hellwig
2021-01-15 18:40 ` Minwoo Im
2021-01-08 14:46 ` Minwoo Im [this message]
2021-01-12 8:08 ` [PATCH 2/3] nvme: check all retry delay times in Identify Controller Christoph Hellwig
2021-01-12 8:40 ` Minwoo Im
2021-01-08 14:46 ` [PATCH 3/3] nvme: add parameter command_retry to enable retry Minwoo Im
2021-01-11 3:47 ` Chao Leng
2021-01-11 12:27 ` Minwoo Im
2021-01-12 9:34 ` Chao Leng
2021-01-12 11:28 ` Minwoo Im
2021-01-12 8:09 ` Christoph Hellwig
2021-01-12 8:44 ` Minwoo Im
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=20210108144659.7126-3-minwoo.im.dev@gmail.com \
--to=minwoo.im.dev@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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