SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


    [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    iSCSI: DLB-T.26 (response for TASK REASSIGN)


    • To: <ips@ece.cmu.edu>
    • Subject: iSCSI: DLB-T.26 (response for TASK REASSIGN)
    • From: "Mallikarjun C." <cbm@rose.hp.com>
    • Date: Tue, 9 Jul 2002 12:20:53 -0700
    • Content-Transfer-Encoding: 7bit
    • Content-Type: text/plain;charset="iso-8859-1"
    • Sender: owner-ips@ece.cmu.edu

    > [T.26] 9.6  Task Management Function Response
    >
    >    For the functions ABORT TASK, ABORT TASK SET, CLEAR ACA, CLEAR TASK
    >    SET, LOGICAL UNIT RESET, TARGET COLD RESET and TARGET WARM RESET, the
    >    target performs the requested Task Management function and sends a
    >    Task Management Response back to the initiator.
    >
    > TASK REASSIGN does not get a response.  Was this intended?
    
    It may be appropriate to include it in this list, but then it would be nice to make sure that the
    target sends the response to the TMF first before acting on the reassigned task (which might
    possibly involve retransmitting an old status sent before the connection failure with a new StatSN).
    Initiators may get confused if the response for the reassigned task arrives prior to the the response
    to the TMF itself (even while there are no StatSN holes).
    
    I suggest:
    
    For all the task management functions defined in 9.5.1, the target performs the requested function and sends a
    Task Management Response back to the initiator.  In the case of the TASK REASSIGN function, the target must
    send the reponse to the task management function request first before acting on the reassigned task.
    
    
    Mallikarjun
    
    


Home

Last updated: Wed Jul 10 06:18:52 2002
11236 messages in chronological order