17.11.2012 Views

MVME5100 Single Board Computer Programmer's Reference Guide

MVME5100 Single Board Computer Programmer's Reference Guide

MVME5100 Single Board Computer Programmer's Reference Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Functional Description<br />

From the perspective of the PCI bus, a better solution would be to select a<br />

PCI FIFO threshold that will allow the bridge lock resolution cycle to<br />

happen early enough to keep the PCI FIFO from getting filled. A similar<br />

case exists with regard to PCI read cycles. Having the bridge lock<br />

resolution associated with a particular PCI FIFO threshold would allow the<br />

PPC Master to get an early enough start at prefetching read data to keep the<br />

PCI Slave from starving for read data.<br />

From the perspective of the PPC bus, a selective FIFO threshold will make<br />

the PPC Slave release the PPC bus at an earlier time thereby reducing<br />

wasted PPC bus bandwidth. PHB offers an option to have the PPC Slave<br />

remove a stalled transaction immediately upon detecting any PCI Slave<br />

activity. This option would help in the case where distributing PPC60x bus<br />

bandwidth between multiple masters is of the utmost importance.<br />

The PHB is tuned to provide the most efficient solution for bridge lock<br />

resolution under normal operating conditions. If further fine tuning is<br />

desired, the WLRT/RLRT (Write Lock Resolution Threshold/Read Lock<br />

Resolution Threshold) fields within the HCSR can be adjusted<br />

accordingly. Note that the FIFO full option exists mainly to remain<br />

architecturally backwards compatible with previous bridge designs.<br />

Speculative PCI Request<br />

There is a case where the processor could get starved for PCI read data<br />

while the PCI Slave is hosting multiple PPC60x bound write cycles. While<br />

attempting to perform a read from PCI space, the processor would<br />

continually get retried as a result of bridge lock resolution.<br />

Between PCI writes, the PPC Master will be taking PPC60x bus bandwidth<br />

trying to empty write posted data, which will further hamper the ability of<br />

the processor to complete its read transaction.<br />

PHB offers an optional speculative PCI request mode that helps the<br />

processor complete read cycles from PCI space. If a bridge lock resolution<br />

cycle happens when the PPC Slave is hosting a compelled cycle, the PCI<br />

Master will speculatively assert a request on the PCI bus. Sometime later<br />

when the processor comes back and retries the compelled cycle, the results<br />

of the PCI Master holding will increase the chance of the processor<br />

successfully completing its cycle.<br />

http://www.motorola.com/computer/literature 2-47<br />

2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!