
PI7C8140A
2-PORT PCI-TO-PCI BRIDGE
Page 20 of 82
March 20, 2007 – Revision 1.01
discards the delayed write completion from the delayed transaction completion queue. The bridge also
conditionally asserts P_SERR# (see Section
5.4).2.5.4
WRITE TRANSACTION BOUNDARIES
The bridge imposes internal address boundaries when accepting write data. The aligned address
boundaries are used to prevent the bridge from continuing a transaction over a device address boundary
and to provide an upper limit on maximum latency. The bridge returns a target disconnect to the
initiator when it reaches the aligned address boundaries under conditions shown in
Table 2-3.Table 2-3. Write Transaction Disconnect Address Boundaries
Type of Transaction
Condition
Aligned Address Boundary
Delayed Write
All
Disconnects after one data transfer
Posted Memory Write
Memory write disconnect control bit = 0
(1)
4KB aligned address boundary
Posted Memory Write
Memory write disconnect control bit = 1
(1)
Disconnects at cache line boundary
Posted Memory Write and
Invalidate
Cache line size
≠ 1, 2, 4, 8, 16
4KB aligned address boundary
Posted Memory Write and
Invalidate
Cache line size = 1, 2, 4, 8, 16
Cache line boundary if posted memory
write data FIFO does not have enough
space for the cache line
Note 1. Memory write disconnect control bit is bit 1 of the chip control register at offset 44h in the configuration space.
2.5.5
BUFFERING MULTIPLE WRITE TRANSACTIONS
The bridge continues to accept posted memory write transactions as long as space for at least one
DWORD of data in the posted write data buffer remains. If the posted write data buffer fills before the
initiator terminates the write transaction, the bridge returns a target disconnect to the initiator.
Delayed write transactions are posted as long as at least one open entry in the delayed transaction queue
exists. Therefore, several posted and delayed write transactions can exist in data buffers at the same
time. See Chapter
5 for information about how multiple posted and delayed write transactions are
ordered.
2.5.6
FAST BACK-TO-BACK TRANSACTIONS
The bridge can recognize and post fast back-to-back write transactions. When the bridge cannot accept
the second transaction because of buffer space limitations, it returns a target retry to the initiator. The
fast back-to-back enable bit must be set in the command register for upstream write transactions, and in
the bridge control register for downstream write transactions.
2.6
READ TRANSACTIONS
Delayed read forwarding is used for all read transactions crossing the bridge. Delayed read transactions
are treated as either prefetchable or non-prefetchable.
Table 2-5 shows the read behavior, prefetchable
or non-prefetchable, for each type of read operation.
07-0067