FCP TRANSFER READY USEAGE

GFRAZIER at AUSVM6.VNET.IBM.COM GFRAZIER at AUSVM6.VNET.IBM.COM
Fri May 5 10:32:04 PDT 1995


FCP login now has two fields which control the use of FCP_XFER_RDY.
These fields, labeled WRITE XFR_RDY DISABLED and READ XFER_RDY DISABLED,
state that when they are disabled, they must NEVER to be used.

This means that when they are disabled, split reads are impossible, and
ALL writes--even multimegabyte writes--MUST be sent without an
FCP_XFER_RDY.

I do not think that this was the intent, especially for writes. Can we make
a wording change to FCP to mean that when FCP_XFER_RDY not disabled, then
(as it already says) XFER_RDY must ALWAYS be used, but when it is enabled,
then it may or may not be used at the option of either the target or the
initiator.

The "Maximum Burst Size" parameter in the disconnect/reconnect Mode page
can continue to limit the amount of data transferred in each sequence as it
does now. This allows a target to limit the amount of data sent to it
immediately after a Write command.

Giles Frazier
IBM Austin
gfrazier at ausvm6.vnet.ibm.com




More information about the T10 mailing list