From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH v2 0/2] nvme_fc: rework io timeouts and termination
Date: Thu, 19 Oct 2017 16:11:37 -0700 [thread overview]
Message-ID: <20171019231139.23611-1-jsmart2021@gmail.com> (raw)
This is a rework of a prior patch that has now been split into two
patches. One patch addresses changes to the io timeout error handler.
The other patch addresses io completions for failing ios to ensure
io retries or to fail commands during association create.
Patches also address prior review comments
James Smart (2):
nvme_fc: correct io termination handling
nvme_fc: correct io timeout behavior
drivers/nvme/host/fc.c | 45 ++++++++++++++++++++++++++++-----------------
1 file changed, 28 insertions(+), 17 deletions(-)
--
2.13.1
next reply other threads:[~2017-10-19 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 23:11 James Smart [this message]
2017-10-19 23:11 ` [PATCH v2 1/2] nvme_fc: correct io termination handling James Smart
2017-10-20 8:15 ` Johannes Thumshirn
2017-10-19 23:11 ` [PATCH v2 2/2] nvme_fc: correct io timeout behavior James Smart
2017-10-20 8:18 ` Johannes Thumshirn
2017-10-20 10:13 ` [PATCH v2 0/2] nvme_fc: rework io timeouts and termination Christoph Hellwig
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=20171019231139.23611-1-jsmart2021@gmail.com \
--to=jsmart2021@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).