Re: iSCSI Clarification (again) for Task Management Commands

["Julian Satran" <Julian_Satran@il.ibm.com>]

Somesh - see 9.4 - Regards, Julo




"Somesh Gupta" <somesh_gupta@silverbacksystems.com>
Sent by: owner-ips@ece.cmu.edu
09-11-01 22:33
Please respond to somesh_gupta

 
        To:     "IPS" <ips@ece.cmu.edu>
        cc: 
        Subject:        iSCSI - Clarification (again) for Task Management Commands

 

On page 67 of the 8-92.txt draft (section 3.5.1), it
says

"For all the tasks covered by the task 
management response (i.e., with CmdSN not higher than the task 
management command CmdSN), additional responses MUST NOT be delivered 
to the SCSI layer after the task management response."

If there is a multiple connection session,
a status for a command impacted by the task
management command (say ABORT TASK SET) could
be stuck in the pipe on one connection, while
the ABORT TASK SET completes on another
connection.

How does the initiator iSCSI enforce the rule above?
Seems to be the equivalent of sending the impacted
commands on other connections in a zombie state,
and not having a very good idea of how to get out.

Similarly Section 9.4 provides additional rules,
but seems to leave a hole open with regards to
status already in flight on other connections.

Any clarifications would be appreciated.

Somesh