UCIE-Memory Access Protocol

Request：

ordered or unordered traffic

response： 

1.support UCIe Memory Request packets on all traffic classes

2.ordering

(1)ordered traffic class - delivered in-order, both request and response

(2) Within an unordered traffic class there are no packet ordering guarantees and the packets may be delivered in any order

(3) Regardless of whether UCIe Memory Request packets are associated with an ordered or an unordered traffic class, a responder may send UCIe Memory Access Response Packets out-of-order (i.e., a responder is not required to send response packets in the same order that the corresponding request packets were received by the responder)

3.status:

(1)Packet Error: malformed UCIe Memory Access Request packet, eg reserved value in the Opcode field, Length field set to zero and the Last DW BE field set to a nonzero value

(2) Programming Model Violation is returned, eg not DWORDs

(3) Retry Request status - should not be used during normal operation and implementations are strongly encouraged to only use the Retry Status when absolutely necessary

The Max Retry Time Units and Max Retry Time Value fields. A requester may use this time duration to determine how long to poll a responder before declaring that the responder has malfunctioned

Access Denied/status Success

request attempts to access an asset that is prohibited, then the asset is not accessed