RE: iSCSI/iWARP drafts and flow control

["Elliott, Robert (Server Storage)" <elliott@hp.com>]

Note that SCSI asynchronous events were declared obsolete by T10 in
November 2002 and have not been documented in SCSI Architecture Model -
3 (SAM-3) since revision 3 (the latest revision is 8).

--
Rob Elliott, elliott@hp.com
Hewlett-Packard Industry Standard Server Storage Advanced Technology
https://ecardfile.com/id/RobElliott




> -----Original Message-----
> From: Mike Ko [mailto:mako@almaden.ibm.com] 
> Sent: Sunday, July 27, 2003 8:31 PM
> To: Caitlin Bestler
> Cc: ips@ece.cmu.edu
> Subject: Re: iSCSI/iWARP drafts and flow control
> 
> 
> Caitlin, it looks like as far as iSCSI asynchronous messages are 
> concerned, we both agree that "setting limits on most of the 
> types listed 
> is so easy that there is no need to negotiate the limit".  So 
> the only 
> other item is the SCSI asynchronous events, and the question 
> yet to be 
> answered is how many AENs can realistically be sent at one 
> time.  Since 
> the optional Shared Receive Queue already provides a solution 
> to handling 
> this situation without impacting the iSCSI spec, does anyone 
> else thinks 
> that the handling of AENs justify adding a negotiable item to 
> set a hard 
> limit on the number of AENs?
> 
> Mike Ko
> IBM Almaden Research
> San Jose, CA 95120