On 06/25/2010 08:39 PM, Eddie Wai wrote:
For cases where the iSCSI disconnection procedure times out due to the iSCSI daemon being slow or unresponsive, the bnx2i_stop routine
Could you describe when iscsid is slow a little more? The unresponsive case sounds like if iscsid is not running, right? For the slow case, it sounds like you are trying to work around a bug in there.
I am also not sure how it helps exactly. iscsid still has to cleanup the iscsi resources like the scsi commands running on the connection (conn stop is called after ep disconnect), so I am not sure how this helps. Does doing it this way skip some steps?
-- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html