From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 0/3] update request retries (loop, rdma, fc)
Date: Thu, 30 Mar 2017 04:23:12 -0700 [thread overview]
Message-ID: <20170330112312.GA29643@infradead.org> (raw)
In-Reply-To: <1490810427-27776-1-git-send-email-sagi@grimberg.me>
On Wed, Mar 29, 2017@09:00:24PM +0300, Sagi Grimberg wrote:
> Keep a consistent behavior with what's checked in the core which
> does not requeue if we exhausted nvme_max_retries.
Looks fine:
Reviewed-by: Christoph Hellwig <hch at lst.de>
But we really need to move this to common code. I'll send a series
to do that, but it will be on top of your series.
prev parent reply other threads:[~2017-03-30 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 18:00 [PATCH 0/3] update request retries (loop, rdma, fc) Sagi Grimberg
2017-03-29 18:00 ` [PATCH 1/3] nvme-rdma: increment request retries counter before requeuing Sagi Grimberg
2017-03-30 8:54 ` Max Gurtovoy
2017-03-29 18:00 ` [PATCH 2/3] nvme-loop: " Sagi Grimberg
2017-03-30 8:54 ` Max Gurtovoy
2017-03-29 18:00 ` [PATCH 3/3] nvme-fc: " Sagi Grimberg
2017-03-30 8:54 ` Max Gurtovoy
2017-03-30 11:23 ` Christoph Hellwig [this message]
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=20170330112312.GA29643@infradead.org \
--to=hch@infradead.org \
/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).