Re: Addition of CmdSN in Data-out PDU

["Julian Satran" <Julian_Satran@il.ibm.com>]

Matthew,

As a basic rule we tried to avoid having fields that have to be checked for consistency by the reciver whenever we could.
Can you be more explicit and help convince us and many others that we should make an exception here.

Regards,
Julo

"BURBRIDGE,MATTHEW (HP-UnitedKingdom,ex2)" <matthew_burbridge@hp.com> 08-10-01 12:30 Please respond to "BURBRIDGE,MATTHEW (HP-UnitedKingdom,ex2)"

To:        ips@ece.cmu.edu, Julian Satran/Haifa/IBM@IBMIL         cc:                 Subject:        Addition of CmdSN in Data-out PDU

Please can the CmdSN be added to the Data-out PDU to improve implementations
when receiving unsolicited Data-out PDUs:

Currently, implementations have to search the command queue list for the
associated command using the ITT as the search criteria.  For solicited
Data-out PDUs this is not an issue as they contain the Target Task Tag.
However, for unsolicated Data PDUs (Target Task Tag = 0xFFFFFFFF) the
locating of the associated command can be greatly enhanced by adding the
Associated CmdSN to Data-out PDU.

Cheers

Matthew Burbridge
Senior Development Engineer
NIS-Bristol
Hewlett Packard
Telnet: 312 7010
E-mail: matthewb@bri.hp.com