System and method for loose ordering write completion for PCI express
View Patent ↗A method for managing the protocol of read/write messages in a PCI Express communication link is disclosed. The method comprises maintaining queues of write requests and read requests associated with each of a plurality of request identifications that are contained in a message header, wherein the read requests associated with a request identification are held in abeyance until such time that write requests associated with the request identification are completed.
1. A method for managing the protocol of read/write messages in a PCI Express communication link comprising:
receiving at least one message associated with each of plurality of data streams;
extracting a request identification (RID) from each of said at least one messages in each of said plurality of data streams;
associating each message with a corresponding request identification,
determining a type of message for each of the at least one received messages associated with a corresponding request identification, said message type selected as at least one of a write message type and a read message type;
outputting said at least one message associated with a write message type associated with a corresponding request identification;
providing an indication that outputting of at least one of said write message type associated with said corresponding request identification is in progress;
determining whether said indication associated with a prior one of said at least one messages indicates outputting of said write message type corresponding to said request identification is in progress;
storing said at least one read message type associated with said corresponding request identification during a period said indication indicates said outputting is in progress;
receiving an indication of completion of outputting of said at least one write message associated with said corresponding request identification;
determining whether additional messages of said write message type are associated with said corresponding request identification and outputting said additional messages of said write message type;
determining whether a message associated with said read message type corresponding to said corresponding request identification is stored after all messages of said write message type associated with said corresponding request identification have been output; and
outputting said read message type.