On 05/30/2016 01:27 AM, Hannes Reinecke wrote: > On 05/25/2016 09:55 AM, mchristi@xxxxxxxxxx wrote: >> From: Mike Christie <mchristi@xxxxxxxxxx> >> >> Currently, if the SCSI eh runs then before we do a LUN_RESET >> we stop the host. This patch and the block layer one before it >> begin to add infrastructure to be able to do a LUN_RESET and >> eventually do a transport level recovery without having to stop the >> host. >> >> For LUn-reset, this patch adds a new callout, eh_async_device_reset_handler, >> which works similar to how LLDs handle SG_SCSI_RESET_DEVICE where the >> LLD manages the commands that are affected. >> >> eh_async_device_reset_handler: >> >> The LLD should perform a LUN RESET that affects all commands >> that have been accepted by its queuecommand callout for the >> device passed in to the callout. While the reset handler is running, >> queuecommand will not be running or called for the device. >> >> Unlike eh_device_reset_handler, queuecommand may still be >> called for other devices, and the LLD must call scsi_done for the >> commands that have been affected by the reset. >> >> If SUCCESS or FAST_IO_FAIL is returned, the scsi_cmnds cleaned up >> must be failed with DID_ABORT. >> > Hmm. With this patch you essentially just replaced the existing > eh_device_reset_handler() with eh_async_device_request_handler(). > So how does this differ from the original behaviour? 1. LLD must call scsi_done and set host byte on each command affected by the reset. This is what they have to do for the SG ioctl reset, but for the scsi eh reset, LLDs do not have to because scsi-ml manages the commands for them. When doing a SG ioctl based reset or if the reset is called from the target like in the last patch it is not possible to have scsi-ml track the outstanding commands like we do today based on timeouts. 2. LLDs have to support commands to other luns during device resets, so they cannot have any sort of host wide device resource lock/resource that they can rely on. It has to be per device. 3. We can now support being able to do a lun reset without having to stop then entire host. > By the time we're calling it the SCSI host is already in EH, ie all > commands have been completed or failed, so why again do we need to > wait for the queue to be empty? I am not sure what you mean here. The patches in this set never go into host reset or even target level reset handling. For this set, we only want to drivers to be able to do a device/lun reset whenever they are asked to do so. > > And how exactly can queuecommand be called for other devices, as the > host is already in EH? > Where in this patchset do we stop the host? -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
