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 V2 0/2] nvme: fixes for command retry
Date: Wed, 13 Jan 2021 23:35:36 +0900 [thread overview]
Message-ID: <20210113143538.554-1-minwoo.im.dev@gmail.com> (raw)
Hello,
This patch series is V2 for Advanced Command Retry Enable(ACRE) feature.
The first patch checks all CRDT(Command Retry Delay Time) [0..2] to
figure out whether CRDT is configured or not.
The other patch has been updated to take internal flag in the controller
instance instead of the module parameter which has been posted in the
previous series [1]. This is based on the review by Chao: Thanks Chao!
Please review.
Thanks,
Since V1:
- The first patch has been applied (Christoph). Removed from this
series.
- Update the last patch to take acre flag from the controller
instance instead of module parameter by updating
nvme_decide_disposition(). (Chao)
[1] https://lore.kernel.org/linux-nvme/20210108144659.7126-1-minwoo.im.dev@gmail.com/T/#t
Minwoo Im (2):
nvme: check all retry delay times in Identify Controller
nvme: retry commands based on ACRE result
drivers/nvme/host/core.c | 18 +++++++++++++++---
drivers/nvme/host/nvme.h | 1 +
2 files changed, 16 insertions(+), 3 deletions(-)
--
2.17.1
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-01-13 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 14:35 Minwoo Im [this message]
2021-01-13 14:35 ` [PATCH V2 1/2] nvme: check all retry delay times in Identify Controller Minwoo Im
2021-01-13 14:35 ` [PATCH V2 2/2] nvme: retry commands based on ACRE result Minwoo Im
2021-01-13 22:20 ` Sagi Grimberg
2021-01-13 22:43 ` Minwoo Im
2021-01-14 2:47 ` Chao Leng
2021-01-14 3:27 ` Minwoo Im
2021-01-14 3:11 ` Keith Busch
2021-01-14 3:28 ` 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=20210113143538.554-1-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