|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: iSCSI : Bridging missing CmdSNs and Abort I/O Error recoverySantosh, You had a possible answer from Matt. However I agree that we might want to address this in text although a solution similar to that suggested by Matt should be by now obvious to every implementer - the target should leave a placeholder in the input queue until the command after gets delivered. Julo Santosh Rao <santoshr@cup.hp.com> on 25/01/2001 21:38:04 Please respond to Santosh Rao <santoshr@cup.hp.com> To: IPS Reflector <ips@ece.cmu.edu> cc: Subject: iSCSI : Bridging missing CmdSNs and Abort I/O Error recovery Julian & All, The draft is currently lacking a section that addresses abort I/O error recovery. Specifically, how is CmdSN bridging issues to be handled in the case where an initiator chooses not to retry an I/O [that failed on a connection failure that affects the delivery of the command to the target or a digest error at the target] because its ULP timer may have expired. In such cases, the initiator can send an Abort Task to inform the target that the I.T.T is being aborted and its corresponding CmdSN can be bridged, instead of having the target stall infinitely in its attempt to enforce ordering and await the missing CmdSN [which is'nt going to arrive, because the initiator did not retry the command]. Regards, Santosh - santoshr.vcf
Home Last updated: Tue Sep 04 01:05:41 2001 6315 messages in chronological order |