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 non-SCSI tasks.



    Hi Santosh:
    
    My .02 (again):
    
    Assuming these transactions are handled in the iSCSI layer:
    
    a) No abort mechanism is required.  Like a 'ping' operation, these functions
    are expected to complete in some fixed time or not at all.
    
    b) A timeout indicates the iSCSI layer is broken -- i.e., timeouts are
    fatal.
    
    Charles
    
    > -----Original Message-----
    > From: Santosh Rao [mailto:santoshr@cup.hp.com]
    > Sent: Tuesday, April 24, 2001 1:31 PM
    > To: Charles Monia
    > Cc: IPS Reflector
    > Subject: Re: iSCSI : Aborting non-SCSI tasks.
    > 
    > 
    > Hi Charles,
    > 
    > non-scsi tasks refers to Login, Logout, Text & NOP-OUT PDUs.
    > 
    > Initiators will need to time these tasks [exchanges ?] and how do they
    > deal with a timeout of such non-scsi tasks [exchanges/PDUs/commands] ?
    > 
    > 
    > Regards,
    > Santosh
    > 
    > 
    > Charles Monia wrote:
    > > 
    > > Hi Santosh:
    > > 
    > > > The iSCSI spec is missing description on how non-SCSI 
    > tasks should be
    > > > aborted
    > > 
    > > What is a non-SCSI task?
    > > 
    > > Charles
    > > > -----Original Message-----
    > > > From: Santosh Rao [mailto:santoshr@cup.hp.com]
    > > > Sent: Tuesday, April 24, 2001 10:27 AM
    > > > To: IPS Reflector
    > > > Subject: iSCSI : Aborting non-SCSI tasks.
    > > >
    > > >
    > > > All,
    > > >
    > > > The iSCSI spec is missing description on how non-SCSI 
    > tasks should be
    > > > aborted in order to flush stale PDUs of that task. Initiators will
    > > > typically time non-SCSI [& SCSI] tasks and will need to 
    > resort to some
    > > > form of abort and cleanup action on a timeout of the 
    > non-scsi task.
    > > >
    > > > This is required in order to safely re-use the task tag resources
    > > > without the danger of stale PDUs arriving from a previous
    > > > incarnation of
    > > > that task tag.
    > > >
    > > > The spec should provide some description on how this is 
    > to be done.
    > > > Perhaps, the semantics of Abort Task can be extended to 
    > non-SCSI tasks
    > > > as well, to avoid defining a second abort mechanism for
    > > > non-SCSI tasks.
    > > >
    > > > - Santosh
    > > >
    > 
    


Home

Last updated: Tue Sep 04 01:04:52 2001
6315 messages in chronological order