From: keith.busch@intel.com (Keith Busch)
Subject: Deprecating NVME_IOCTL_SUBSYS_RESET
Date: Thu, 10 May 2018 10:52:04 -0600 [thread overview]
Message-ID: <20180510165203.GC4477@localhost.localdomain> (raw)
In-Reply-To: <74d5123de0b94d38b08ed85678d2ac91@ausx13mps321.AMER.DELL.COM>
On Thu, May 10, 2018@04:18:06PM +0000, Alex_Gagniuc@Dellteam.com wrote:
>
> According to (my reading of) the NVMe spec, an NSSR and PCIe link reset
> should be equivalent.
That can't possibly be the case. A PCIe link reset affects a single
device on that PCIe link, but a NSSR resets ALL controllers in the
subsystem, some of which may be on different links.
The NSSR does indeed lead to a PCIe link reset, but there's a lot more
to it that that.
> > That said, I have heard enough cases where this reset method is not
> > successful, so there's some work to do here. Most failures seem to be
> > around the handling of the rapid link down-up sequence, and success
> > seems very dependent on the platform and the device used.
>
> There is also the controller reset, which seems less intrusive, though I
> haven't looked into it. Can that be used instead of the subsystem reset
> for those cases where a subsystem reset is allegedly needed?
According to the spec (section 5.11 Firmware Commit), a device may to
require a subsystem reset in order to complete a firmware upgrade. No
other type of reset will do the trick.
prev parent reply other threads:[~2018-05-10 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 15:06 Deprecating NVME_IOCTL_SUBSYS_RESET Alex G.
2018-05-10 16:13 ` Keith Busch
2018-05-10 16:18 ` Alex_Gagniuc
2018-05-10 16:52 ` Keith Busch [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=20180510165203.GC4477@localhost.localdomain \
--to=keith.busch@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.