PI7C8150AND datasheet(27/111 Pages) PERICOM

27 / 111 page

PI7C8150A

2-PORT PCI-TO-PCI BRIDGE

Page 27 of 111

APRIL 2006 – Revision 1.1

3.6

READ TRANSACTIONS

Delayed read forwarding is used for all read transactions crossing PI7C8150A. Delayed

read transactions are treated as either prefetchable or non-prefetchable. Table 3-5 shows the

read behavior, prefetchable or non-prefetchable, for each type of read operation.

3.6.1

PREFETCHABLE READ TRANSACTIONS

A prefetchable read transaction is a read transaction where PI7C8150A performs

speculative DWORD reads, transferring data from the target before it is requested from the

initiator. This behavior allows a prefetchable read transaction to consist of multiple data

transfers. However, byte enable bits cannot be forwarded for all data phases as is done for

the single data phase of the non-prefetchable read transaction. For prefetchable read

transactions, PI7C8150A forces all byte enable bits to be turned on for all data phases.

Prefetchable behavior is used for memory read line and memory read multiple transactions,

as well as for memory read transactions that fall into prefetchable memory space.

The amount of data that is pre-fetched depends on the type of transaction. The amount of

pre-fetching may also be affected by the amount of free buffer space available in

PI7C8150A, and by any read address boundaries encountered.

Pre-fetching should not be used for those read transactions that have side effects in the

target device, that is, control and status registers, FIFO’s, and so on. The target device’s

base address register or registers indicate if a memory address region is prefetchable.

3.6.2

NON-PREFETCHABLE READ TRANSACTIONS

A non-prefetchable read transaction is a read transaction where PI7C8150A requests one

and only one DWORD from the target and disconnects the initiator after delivery of the

first DWORD of read data. Unlike prefetchable read transactions, PI7C8150A forwards the

read byte enable information for the data phase.

Non-prefetchable behavior is used for I/O and configuration read transactions, as well as

for memory read transactions that fall into non-prefetchable memory space.

If extra read transactions could have side effects, for example, when accessing a FIFO, use

non-prefetchable read transactions to those locations. Accordingly, if it is important to

retain the value of the byte enable bits during the data phase, use non-prefetchable read

transactions. If these locations are mapped in memory space, use the memory read

command and map the target into non-prefetchable (memory-mapped I/O) memory space

to use non-prefetching behavior.

06-0057

PI7C8150AND Datasheet(PDF) 27 Page - Pericom Semiconductor Corporation