From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: Limit command retries
Date: Sun, 10 Jul 2016 02:47:42 -0700 [thread overview]
Message-ID: <20160710094742.GB5897@infradead.org> (raw)
In-Reply-To: <20160622170122.GH1448@localhost.localdomain>
On Wed, Jun 22, 2016@01:01:22PM -0400, Keith Busch wrote:
> On Wed, Jun 22, 2016@09:14:42AM -0700, Christoph Hellwig wrote:
> > How urgent is this patch? If it fixes an actual major issue seen
> > in the field we should probably but the ->retries use in as-is,
> > otherwise I'd prefer to avoid introducing more users of it for now.
>
> Cool, thanks. This is not an urgent issue for us, but was hoping to make
> the 4.8 window. If we can flush something better out, I'm happy to wait.
Given that even the prep patches for that work aren't merged yet
they aren't likely to make it for 4.8.
Based on that I think we should get this patch in for the merge window:
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2016-07-10 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 17:44 [PATCH] nvme: Limit command retries Keith Busch
2016-06-22 10:30 ` Sagi Grimberg
2016-06-22 14:40 ` Keith Busch
2016-06-22 16:14 ` Christoph Hellwig
2016-06-22 17:01 ` Keith Busch
2016-07-10 9:47 ` Christoph Hellwig [this message]
2016-07-12 23:21 ` Jens Axboe
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=20160710094742.GB5897@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).