Question on Patch - NVMe: Shutdown controller only for power-off

Keith Busch keith.busch at intel.com
Tue Jun 7 11:55:45 PDT 2016


On Tue, Jun 07, 2016 at 06:42:00PM +0000, Jeff Lien wrote:
> Keith,
> The issue isn't that the fw activate requires a shutdown; it's more that the HGST controller takes much longer to execute the nvme_disable_ctrl if it hasn't been shutdown first.  This issue caused us to add a longer delay before the first read of the csts reg in nvme_wait_ready.
> 
> Rather than adding a delay in nvme_disable_controller, I think the better option would be to shutdown the controller.  The comment says "If we're called to reset a live controller first shut it down" so in this case I think the shutdown parm should be true.

I'll change the comment to say "disable" instead of "shut down". We
want to reserve controller shutdown to power loss scenarios per spec
recommendations, which this is not. A controller reset is generally much
faster than a shutdown, which is why we don't toggle CC.SHN here.



More information about the Linux-nvme mailing list