SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


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

    RE: iSCSI: aborting an immediate command with ABORT TASK



    I agree.  This sounds like a good solution to me.
    
    Thanks for listening!
    
    Tony
    
    > -----Original Message-----
    > From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On Behalf Of
    > Eddy Quicksall
    > Sent: Thursday, September 05, 2002 5:44 PM
    > To: 'Julian Satran'; ips@ece.cmu.edu
    > Cc: Black_David@emc.com
    > Subject: RE: iSCSI: aborting an immediate command with ABORT TASK
    > 
    > 
    > The two last EMAIL's you sent regarding this work for me.
    > 
    > Eddy
    > 
    > -----Original Message-----
    > From: Julian Satran [mailto:Julian_Satran@il.ibm.com]
    > Sent: Thursday, September 05, 2002 3:05 PM
    > To: ips@ece.cmu.edu
    > Cc: Black_David@emc.com
    > Subject: RE: iSCSI: aborting an immediate command with ABORT TASK
    > 
    > 
    > In addition in order to eliminate the "corner case" I 
    > mentioned earlier
    > (and that is the only ambiguity we know about) - that a TASK ABORT may
    > abort
    > both an immediate and a non-immediate that have the same 
    > number and are
    > both lost even though only the immediate was intended I added 
    > the following
    > text to 9
    > 
    >        If an ABORT TASK is issued for a task created by an immediate
    >        command then RefCmdSN MUST be that of the Task 
    > Management request
    >        itself (i.e. CmdSN and RefCmdSN are equal; otherwise 
    > RefCmdSN MUST
    >        be set to the CmdSN of the task to be aborted (lower 
    > than CmdSN).
    > 
    >  and made 9.5.5 to raed:
    > 
    >    RefCmdSN
    > 
    > 
    >        If an ABORT TASK is issued for a task created by an immediate
    >        command then RefCmdSN MUST be that of the Task 
    > Management request
    >        itself (i.e. CmdSN and RefCmdSN are equal).
    > 
    >        For an ABORT TASK of a task created by non-immediate command
    >        RefCmdSN MUST be set to the CmdSN of the task identified by the
    >        Referenced Task Tag field. Targets must use this field 
    > as described
    >        in section 9.6.1 when the task identified by the 
    > Referenced Task Tag
    >        field is not with the target.
    > 
    >        Otherwise, this field is reserved.
    > 
    >     Regards,
    >     Julo
    > 
    > ----- Forwarded by Julian Satran/Haifa/IBM on 05/09/02 21:56 -----
    >  
    > 
    >                       Julian Satran
    > 
    >                                                To:       
    > ips@ece.cmu.edu
    > 
    >                       05/09/02 19:26           cc:
    > 
    >                                                From:     Julian
    > Satran/Haifa/IBM@Haifa/IBM@IBMIL
    > 
    >                                                Subject:  RE: 
    > iSCSI: aborting
    > an immediate command with ABORT TASK                               
    >  
    > 
    >  
    > 
    >  
    > 
    > 
    > 
    > 
    > Forget the previous text - we wont the clarification to be 
    > added for the
    > "plugging side" (the target) and the we suggest changing the 
    > last bullet b
    > in 9.6.1
    > to:
    > 
    >           If the Referenced Task Tag does not identify an 
    > existing task,
    >           but if the CmdSN indicated by the RefCmdSN field in the Task
    >           Management function request is within the valid 
    > CmdSN window and
    >           less than the CmdSN of the Task Management function request
    >           itself, then targets must consider the CmdSN 
    > received and return
    >           the "Function complete" response.
    > 
    >  We thought this was obvious from the overview text but it 
    > apparently is
    >  not.
    > 
    >  Julo
    > 
    > The current wording IS CORRECT!
    > 
    > 
    > 
    > 
    


Home

Last updated: Fri Sep 06 12:18:55 2002
11786 messages in chronological order