![](http://datasheet.mmic.net.cn/Pericom/PI7C7300DNAE_datasheet_99372/PI7C7300DNAE_50.png)
PI7C7300D
3-PORT PCI-TO-PCI BRIDGE
Page 50 of 107
Pericom Semiconductor
November 2005 - Revision 1.01
PI7C7300D does not combine separate write transactions into a single write
transaction—this optimization is best implemented in the originating master.
PI7C7300D does not merge bytes on separate masked write transactions to the same
DWORD address—this optimization is also best implemented in the originating
master.
PI7C7300D does not collapse sequential write transactions to the same address into
a single write transaction—the PCI Local Bus Specification does not permit this
combining of transactions.
6.2
GENERAL ORDERING GUIDELINES
Independent transactions on primary and secondary buses have a relationship only when
those transactions cross PI7C7300D.
The following general ordering guidelines govern transactions crossing PI7C7300D:
The ordering relationship of a transaction with respect to other transactions is
determined when the transaction completes, that is, when a transaction ends with a
termination other than target retry.
Requests terminated with target retry can be accepted and completed in any order
with respect to other transactions that have been terminated with target retry. If the
order of completion of delayed requests is important, the initiator should not start a
second delayed transaction until the first one has been completed. If more than one
delayed transaction is initiated, the initiator should repeat all delayed transaction
requests, using some fairness algorithm. Repeating a delayed transaction cannot be
contingent on completion of another delayed transaction. Otherwise, a deadlock can
occur.
Write transactions flowing in one direction have no ordering requirements with
respect to write transactions flowing in the other direction. PI7C7300D can accept
posted write transactions on both interfaces at the same time, as well as initiate
posted write transactions on both interfaces at the same time.
The acceptance of a posted memory write transaction as a target can never be
contingent on the completion of a non-locked, non-posted transaction as a master.
This is true for PI7C7300D and must also be true for other bus agents. Otherwise, a
deadlock can occur.
PI7C7300D accepts posted write transactions, regardless of the state of completion
of any delayed transactions being forwarded across PI7C7300D.
6.3
ORDERING RULES
Table 6-1 shows the ordering relationships of all the transactions and refers by number to
the ordering rules that follow.
Table 6-1 SUMMARY OF TRANSACTION ORDERING
Pass
Posted
Write
Delayed
Read
Request
Delayed
Write
Request
Delayed Read
Completion
Delayed Write
Completion
Posted Write
No
1
Yes
5
Yes
5
Yes
5
Yes
5
Delayed Read Request
No
2
No
Yes