From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v2] NVMe: Add controller state for scheduling resets
Date: Wed, 8 Jun 2016 05:03:29 -0700 [thread overview]
Message-ID: <20160608120329.GA20526@infradead.org> (raw)
In-Reply-To: <575808AC.2030004@lightbits.io>
On Wed, Jun 08, 2016@02:59:40PM +0300, Sagi Grimberg wrote:
> Is my understanding correct? Do you think that we should modify the
> loop and rdma drivers to do async reset as well?
>
> This also makes the different transport behave differently at the moment
> which is something we should strive to avoid...
Don't worry, I have an almost ready patch series to pull this change
it in, it actually helps for fabrics as well.
next prev parent reply other threads:[~2016-06-08 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 21:18 [PATCH v2] NVMe: Add controller state for scheduling resets Keith Busch
2016-05-31 21:31 ` Keith Busch
2016-06-08 11:59 ` Sagi Grimberg
2016-06-08 12:03 ` Christoph Hellwig [this message]
2016-06-08 12:11 ` Sagi Grimberg
2016-06-08 13:04 ` 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=20160608120329.GA20526@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